In December 2017, a new status code (103) was added to the HTTP standard, and as one prominent OCS provider now uses this status code, Attica needs to be able to handle it more gracefully than just reporting an unknown OCS error (which is reported to the user, but has no actual effect on things). As it is a benign status, we simply accept it and forward it to the consumer as being not an error. Specifically, we do this by changing from accepting only status 100 as an informational status, to accepting any informational status (since any actual errors are reported through other status codes).
Details
Details
- Reviewers
ngraham - Group Reviewers
KNewStuff Frameworks - Commits
- R235:7e988d655db2: Accept any HTTP status between 100 and 199 as benign
Diff Detail
Diff Detail
- Repository
- R235 Attica
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Comment Actions
Hmm... You're probably right, yes, 100 is supposed to be all benign status type stuff, so... yeah, i'll do a quick update with that instead.
Comment Actions
Just accept any informational status as benign, rather than the specifically picked ones.