Be consistent in reading revision headers #10563
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ContextHandler uses the first RevisonName/Namespace header, whereas RequestLog uses the last.
In practice the Revision headers are added by AppendHeaders which (confusingly) actually overwrites rather than appending, so there's only ever one value of the header so this doesn't make any difference -- but doing it the same way in both places is (a) nicer / less confusing and (b) lets us drop our custom LastHeaderValue function in favour of using the standard golang net/http header.Get in both places.
/assign @markusthoemmes @vagababov