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

REXML::ParseException parsing 401 Unauthorized response body #22

Closed
marcoshack opened this issue Jan 15, 2010 · 2 comments
Closed

REXML::ParseException parsing 401 Unauthorized response body #22

marcoshack opened this issue Jan 15, 2010 · 2 comments

Comments

@marcoshack
Copy link

Should savon cares about the body of a 401 status response? I believe the parsing exception [1] is preventing the client to authenticate, but the body content is completely useless here, right?

Best,
Marcos Hack.

[1] http://gist.github.com/278088

@rubiii
Copy link
Contributor

rubiii commented Jan 16, 2010

i don't think the exception prevents you from authentication. it's actually raised much later. so by looking at the debug output and seeing your server returning a 401, i don't think you're passing any authentication credentials.

please take a look at the document or specs:
http://wiki.github.com/rubiii/savon/request
https://github.com/rubiii/savon/blob/master/spec/integration/http_basic_auth_spec.rb

talking about the exception: i added a fix for this problem to the current dev branch:
https://github.com/rubiii/savon/commit/9650dc1168e7ab1cfbcbeca7f1a03d8fea179fca

this fix will be included in the next release and i'll leave the issue open until it's available.

@rubiii
Copy link
Contributor

rubiii commented Jan 17, 2010

released version 0.7.2 including a fix for this issue.

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

No branches or pull requests

2 participants