Skip to content

Don't respond with 302 for post/put/head. #46

Merged
merged 1 commit into from Feb 15, 2012

2 participants

@cfis
cfis commented Jan 10, 2012

Here is a proposed fix for #44.

Thanks - Charlie

@rtomayko
Owner

Merging this. I still haven't verified that limiting to GET/HEAD is the right thing and I'm pretty sure 302 is a valid response for PUT and maybe OPTIONS but this seems like a good enough fix for a real problem so let's go with it for now.

@rtomayko rtomayko merged commit 5104c34 into rtomayko:master Feb 15, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.