[PATCH] entity body in 201 responses

Julian Reich jreich at jreich.com
Tue Dec 29 12:36:53 MSK 2009


at the moment nginx (stable+development) does not encode the entity body of a response with status 201 (Created) using chunked transfer encoding.
(It sends the unencoded entity body though => the client ends up receiving neither a Content-Length header nor a chunked entity body.)
As RFC 2616 encourages sending an entity body along with 201 responses the attached patch should probably be applied.

Julian Reich

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 201-chunked-entity-body.patch
Type: application/octet-stream
Size: 614 bytes
Desc: not available
URL: <http://nginx.org/pipermail/nginx-devel/attachments/20091229/9e843bca/attachment.obj>

More information about the nginx-devel mailing list