> On Apr 16, 2015, at 5:54 PM, Alan Carroll
> wrote:
>
> 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 w
I would find something where I can make programmatic decisions based on the
general class of error, e.g. "was a client side problem" "was a cache related
problem"
"was an origin connection problem" "was a protocol violation" most useful.
While also being able to get the specific error values.
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).
