-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow 1xx status codes #871
Conversation
Travis is unhappy due to formatting. Can you run Maven package locally? The build will fix any formatting for you. Once complete, please push a new commit. |
Sorry about that! It should hopefully be fixed now |
@maly7 our typical process is for one of the maintainers to review, and if approved, we give the others a few days to weigh in. After that, if there are no additional comments, we'll merge your PR. Thanks for your help! |
Thanks! Don't worry about the travis failures, there is an issue with the HTTP2 test case that is not related to your changes. |
* add support for 1xx status codes in Response * allow for any status code
* add support for 1xx status codes in Response * allow for any status code
Previously Response didn't allow status codes in the 1xx series, only 200 and beyond were allowed. This fixes that by allowing status codes in the range from 100 <= status < 600.
Fixes #836