Skip to content

Conversation

@mlibbey
Copy link
Contributor

@mlibbey mlibbey commented Jan 16, 2020

No description provided.

@randall randall added this to the 10.0.0 milestone Jan 16, 2020
@randall
Copy link
Contributor

randall commented Jan 16, 2020

@bryancall This should also go into 8.0.x


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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least for us, Akamai does not expose multiple layers for their equivalent, X-cache and X-cache-remote -- both are single layer only.

@mlibbey mlibbey merged commit b670607 into apache:master Feb 4, 2020
@mlibbey mlibbey deleted the xcache branch February 4, 2020 00:01
@zwoop zwoop modified the milestones: 10.0.0, 9.0.0 Feb 5, 2020
@zwoop zwoop modified the milestones: 9.0.0, 8.1.0 Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants