> On Apr 16, 2015, at 3:39 PM, Alan M. Carroll
> wrote:
>
> Based on some discussions here at the summit, we would like to add the
> ability for the core to report certain error conditions to plugins. We have
> at least one use case where it is critical to be able to distinguish
> different
A third option is to add an API and data on the HTTP state machine to store the
error code. This has the issue that it's harder to have multiple conditions
active. On the other hand it's not overloading some other mechanism and would
be faster (by comparing number values instead of strings).
Based on some discussions here at the summit, we would like to add the ability
for the core to report certain error conditions to plugins. We have at least
one use case where it is critical to be able to distinguish different causes
for a 502 error (origin server down, cache write lock missed, e
Based on some discussions here at the summit, we would like to add the ability
for the core to report certain error conditions to plugins. We have at least
one use case where it is critical to be able to distinguish different causes
for a 502 error (origin server down, cache write lock missed, e
Github user jacksontj commented on the pull request:
https://github.com/apache/trafficserver/pull/183#issuecomment-93805512
Can you try applying 5a367b6 to your tsqa? I think the wsgiserver I'm using
right now only supports a single connection-- this should make it multithreaded
and h
Github user ffcai commented on the pull request:
https://github.com/apache/trafficserver/pull/183#issuecomment-93790194
I just find that the local httpbin (start with like `gunicorn httpbin:app`)
acts different with http://httpbin.org. And, this test case fails for local
httpbin :( .
