-
Notifications
You must be signed in to change notification settings - Fork 120
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
Send Content-Type only if there is data, relative post location #32
Conversation
The content type issue addressed here causes issues with servers that are very strict - for example senchalabs/connect#680. Would be nice to see this fixed (for GET requests too). |
Looks good to me. |
If we get 201 response with no location header, treat is as 200
Make slumber not crash on 201 response without Location header
Can we not get this merged? |
@alithorn still "active", maintenance mostly - I'll get this merged when I get a moment. |
@samgiles I apologize if I sound(ed) presumptuous. Starting a large project and I seriously appreciate the abstraction you are providing but I'm shit scared of having to support a branch of my own if it takes 3 years to get a good change merged... |
The content-type issue is now in master, tracking the location stuff in #138, will need to check test coverage. |
…payload is None
Sorry for two fixes in single pull request.
PUT
andDELETE
methods should only sendContent-type
header if there request has data.If
Location
header is not full URL (doesn't start with http/s) it can be passed asid
parameter andurl_join
function will joinLocation
withbase_path
.