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

Send Content-Type only if there is data, relative post location #32

Closed
wants to merge 5 commits into from

Conversation

bancek
Copy link

@bancek bancek commented Jul 15, 2012

Sorry for two fixes in single pull request.

PUT and DELETE methods should only send Content-type header if there request has data.

If Location header is not full URL (doesn't start with http/s) it can be passed as id parameter and url_join function will join Location with base_path.

@evdb
Copy link

evdb commented Nov 29, 2012

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).

@merwok
Copy link
Contributor

merwok commented Mar 7, 2013

Looks good to me.

bancek and others added 3 commits March 21, 2013 02:30
If we get 201 response with no location header, treat is as 200
Make slumber not crash on 201 response without Location header
@atlithorn
Copy link

Can we not get this merged?
Is slumber no longer active?

@samgiles
Copy link
Owner

@alithorn still "active", maintenance mostly - I'll get this merged when I get a moment.

@samgiles samgiles self-assigned this Mar 23, 2016
@atlithorn
Copy link

@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...

@samgiles
Copy link
Owner

The content-type issue is now in master, tracking the location stuff in #138, will need to check test coverage.

@samgiles samgiles closed this Apr 24, 2017
gusibi pushed a commit to gusibi/slumber that referenced this pull request Jul 25, 2018
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.

5 participants