[GitHub] trafficserver issue #1575: 5xx response instead of stale content

[mlibbey]

Github user mlibbey commented on the issue:

https://github.com/apache/trafficserver/issues/1575
  
This is 
proxy.config.http.negative_revalidating_enabled which is disabled by 
default.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1575: 5xx response instead of stale content

[mlibbey]

Github user mlibbey closed the issue at:

https://github.com/apache/trafficserver/issues/1575


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1575: 5xx response instead of stale content

[mlibbey]

Github user mlibbey commented on the issue:

https://github.com/apache/trafficserver/issues/1575
  
- in whatever fix we do, should make sure that the CC:must-revalidate does 
return the 5xx error (eg, the must-revalidate does not allow for serving stale


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1575: 5xx response instead of stale content

[mlibbey]

GitHub user mlibbey opened an issue:

https://github.com/apache/trafficserver/issues/1575

5xx response instead of stale content

Stale content should be used when available over general transient errors. 
However, once ATS gets a 5xx error, it will return the 5xx to the user instead 
of stale content.

To reproduce: 
- set up ats and an origin
- get an object cached. Wait for the object to expire

Then perform these tests:
1) serve stale with origin unavailable:
- fetch the object. 
- you will (and should) get the stale object. 
This is expected and desired behavior 👍 

2) 5xx error case:
- have the origin respond 502/504 (like a parent)... for the object
- fetch the object-- you will get a 502-- you should get the stale object
- turn off the origin and refetch-- you will still get the 502. 
In these cases the via header will report hit-stale, so the object is still 
in cache, just isn't served. We expect a stale object instead of the transient 
error.







---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---