Document the order of the X-Cache header#6328
Merged
mlibbey merged 1 commit intoapache:masterfrom Feb 4, 2020
Merged
Conversation
randall
approved these changes
Jan 16, 2020
Contributor
|
@bryancall This should also go into 8.0.x |
zwoop
reviewed
Jan 16, 2020
|
|
||
| If a request goes through multiple proxies, each one prepends its X-Cache header content | ||
| at the beginning of the existing X-Cache header. As a result, the order is reversed from | ||
| the Via: header. |
Contributor
There was a problem hiding this comment.
Nice. I wonder, since the behavior of the Via header is pretty darn well known (and defined), should we not adhere to this for X-Cache too ? What does Akamai do ?
Contributor
Author
There was a problem hiding this comment.
At least for us, Akamai does not expose multiple layers for their equivalent, X-cache and X-cache-remote -- both are single layer only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.