no content length on 204s; hangs wget
Jeff Kaufman
jefftk at google.com
Mon Apr 8 18:39:07 UTC 2013
I've written a content handler for nginx that does:
return NGX_HTTP_NO_CONTENT;
This produces output like:
$ curl -D- 'http://localhost:8050/no_content_test'
HTTP/1.1 204 No Content
Server: nginx/1.2.7
Connection: keep-alive
Date: Mon, 08 Apr 2013 18:28:02 GMT
Testing this in curl it's fine, but wget waits for a content header,
timing out after 60s. I tried doing the opposite of
ngx_http_clear_content_length to set a content length, but it doesn't
get sent.
Is there a way to add a Content-Length on a 204 response or is this a wget bug?
Jeff
Full source: https://github.com/pagespeed/ngx_pagespeed/blob/3ae84a3c17d78046477eae68e98a5f50405a292a/src/ngx_pagespeed.cc#L2053
More information about the nginx-devel
mailing list