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.

Sign up for GitHub

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

Jump to bottom

HTTP POST should return 201 Created #105

Merged
merged 1 commit into from May 18, 2015
Merged

HTTP POST should return 201 Created #105

merged 1 commit into from May 18, 2015

Conversation

abargnesi
Copy link
Contributor

This is more semantically correct when the Location header is returned.

@abargnesi
HTTP POST should return 201 Created
a5c995c 
This is more semantically correct when the Location header is returned.
@syndbg
Copy link
Contributor

syndbg commented May 15, 2015

👍

@ghost
Copy link

ghost commented May 17, 2015

From w3.org

10.2.2 201 Created

The request has been fulfilled and resulted in a new resource being created.

10.2.3 202 Accepted

The request has been accepted for processing, but the processing has not been completed.

I think this is merge-able message.save is being created not processing.

kgrz added a commit that referenced this pull request May 18, 2015
@kgrz
Merge pull request #105 from abargnesi/post_returns_201_created
509a3ea 
HTTP POST should return 201 Created
@kgrz kgrz merged commit 509a3ea into sinatra:master May 18, 2015
@kgrz
Copy link
Member

kgrz commented May 18, 2015

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@abargnesi @syndbg @kgrz