> On Apr 16, 2015, at 5:54 PM, Alan Carroll > <solidwallofc...@yahoo-inc.com.INVALID> 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 would be faster (by comparing number values instead of strings). > >
I think this has a lot of potential, and we can also add a new log tag that lets you at least “dump” the error codes / state. They don’t have to be pretty, requiring a decoder ring to figure out what the error is in the log for this would be fine IMO (we have other less flexible, but more descriptive error tags already). — Leif
