GitHub user maskit opened an issue:
https://github.com/apache/trafficserver/issues/1627
TSHttpTxnAborted is not documented
TSHttpTxnAborted is not documented.
It returns TSReturnCode (TS_SUCCESS | TS_ERROR), and it's very unclear
whether a transaction is aborted or not.
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1625
version?
---
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
Github user mlibbey commented on the issue:
https://github.com/apache/trafficserver/issues/1626
How about if I add:
That is, when enabled, |TS| will serve stale when it can not reach the
origin server (similar to the stale-if-error Cache-Control directive).
---
If your project
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1531
I got this again on Docs.
```
(gdb) bt full
#0 0x2b5b8bd881d7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
GitHub user zwoop reopened an issue:
https://github.com/apache/trafficserver/issues/1531
Assertion in state_read_server_response_header (v7.1.0)
Seeing this on docs (infrequently):
```
(gdb) bt full
#0 0x757b21d7 in __GI_raise (sig=sig@entry=6) at
Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1620
You can commit it, but I'm going to modify the documents to use the correct
term "IP address" instead of just "IP" which, sir, is *wrong*.
---
If your project is set up for it, you
Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/issues/1626
The documentation is not completely clear. If this is enabled, then on
*subsequent* requests to the failed object, ATS will revalidate the negatively
cached item against the
