You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2020/09/29 20:41:18 UTC
[GitHub] [trafficserver] ezelkow1 opened a new issue #7227: s-maxage not respected with authorization headers
ezelkow1 opened a new issue #7227:
URL: https://github.com/apache/trafficserver/issues/7227
Testing for some issues I came across this problem, according to the rfc:
https://tools.ietf.org/html/rfc7234#section-3.2
3.2. Storing Responses to Authenticated Requests
A shared cache MUST NOT use a cached response to a request with an
Authorization header field (Section 4.2 of [RFC7235]) to satisfy any
subsequent request unless a cache directive that allows such
responses to be stored is present in the response.
In this specification, the following Cache-Control response
directives (Section 5.2.2) have such an effect: must-revalidate,
public, and s-maxage.
I tested here having s-maxage on a cached object, then sent requests with an auth header and it would always go upstream for the request as long as an auth header was attached. The only way to cache them was with the addition of `public` to the CC header
This was with 8.1.x
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] ezelkow1 commented on issue #7227: s-maxage not respected with authorization headers
Posted by GitBox <gi...@apache.org>.
ezelkow1 commented on issue #7227:
URL: https://github.com/apache/trafficserver/issues/7227#issuecomment-987553973
> The below section of the cache-test will be green if this is fixed?
>
> > An optimal HTTP shared cache reuses a response to a request that contained Authorization, if it has Cache-Control: s-maxage
>
> https://cache-tests.fyi/#auth
>
> ( I think we had this cache-test on our ci before...I don't know where it is now )
yea Ive added it to my list to go and fix cache-tests on the new ci. We had it working a while back but since we had to shuffle around its network configuration and hosting the cache-tests hosting container got lost. So its on my list to go fix when I get a chance
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] masaori335 commented on issue #7227: s-maxage not respected with authorization headers
Posted by GitBox <gi...@apache.org>.
masaori335 commented on issue #7227:
URL: https://github.com/apache/trafficserver/issues/7227#issuecomment-987456812
The below section of the cache-test will be green if this is fixed?
> An optimal HTTP shared cache reuses a response to a request that contained Authorization, if it has Cache-Control: s-maxage
https://cache-tests.fyi/#auth
( I think we had this cache-test on our ci before...I don't know where it is now )
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] github-actions[bot] commented on issue #7227: s-maxage not respected with authorization headers
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #7227:
URL: https://github.com/apache/trafficserver/issues/7227#issuecomment-930684640
This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org