Support '204 No Content' status code #227

merged 1 commit into from May 29, 2013


None yet
3 participants

iamFIREcracker commented May 6, 2013

Writing REST APIs often requires one end-point to return an empty response even if the client is expecting a JSON/XML object.

Instead of making the server return an explicit empty object (e.g. {}), a better solution is to send a '204 No Content' message back to the client.

On stackoverflow I found a small discussion on the subject:

oxtopus commented May 29, 2013

Merge, please. I've had to basically re-implement this on my own. Glad to see someone already had an open pull request, otherwise I would have opened one.

@anandology anandology added a commit that referenced this pull request May 29, 2013

@anandology anandology Merge pull request #227 from iamFIREcracker/patch-1
Support '204 No Content' status code

@anandology anandology merged commit 6b86a40 into webpy:master May 29, 2013

1 check passed

default The Travis build passed

anandology commented May 29, 2013

@oxtopus merged!

@iamFIREcracker thanks for the pull request.

oxtopus commented May 29, 2013


iamFIREcracker deleted the iamFIREcracker:patch-1 branch May 29, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment