Skip to content
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

Return HTTP response even on non-2XX responses. Clients might want it. #9

Merged
merged 1 commit into from Sep 4, 2013

Conversation

deet
Copy link

@deet deet commented Sep 4, 2013

For #8

mrjones added a commit that referenced this pull request Sep 4, 2013
Return HTTP response even on non-2XX responses. Clients might want it.
@mrjones mrjones merged commit c391ce5 into mrjones:master Sep 4, 2013
@mrjones
Copy link
Owner

mrjones commented Sep 4, 2013

Thanks!!

@deet
Copy link
Author

deet commented Sep 5, 2013

You're welcome! Thanks for the library.

And sorry for the two issues instead of one.

I've run into some other issues with using this function and those that return its result, and I'm not sure how they should be addressed. (Let me know if you want this as a separate issue.) Specifically, clients can't determine whether the call failed due to network error or because of something application-level (like non-2XX response). So far it seems necessary to do a substring match for "HTTP response is not 200/OK as expected" to determine that the call failed due to a server response. Any suggestions?

@mrjones
Copy link
Owner

mrjones commented Sep 17, 2013

( FYI: Moved this to a new issue. See the discussion in #11 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants