fixed response code handling

[aklinkert]

Hey @dghubble ,

thanks for merging the other PR #10. This one adds two checks for http status code 201, which is used by Xing OAUTH1 Api introduced in #10. Would be cool if we could get this one in soon.

We could actually think about allowing some more, but I guess these can also be added when some different APIs require them, yah?

Thanks and greetings from Germany!
Alex

[dghubble]

Probably better to allow any 2XX. Now that the response code is checked, I imagine there will be other providers using other codes in the range.

[aklinkert]

When having a look onto the status code list I'm wondering if there is a situation where an oauth endpoint would send a status code ! [200, 201]? Guess that's very unlikely since the rest is either no content or partial content, which won't be used here, no?

[dghubble]

Yeah, fine. I bet someone else has a weird implementation, but they can raise that concern then. LGTM