15 messages in ru.sysoev.nginxhead requests and chunked transfer en...
FromSent OnAttachments
Spil GamesOct 1, 2008 2:04 am 
Igor SysoevOct 1, 2008 2:19 am.head
Robert GabrielOct 1, 2008 3:32 am 
Igor SysoevOct 1, 2008 4:14 am.head1
Spil GamesOct 1, 2008 4:57 am 
Robert GabrielOct 1, 2008 5:01 am 
Spil GamesOct 1, 2008 5:03 am 
Grzegorz NosekOct 1, 2008 5:04 am 
Robert GabrielOct 1, 2008 5:06 am 
Robert GabrielOct 1, 2008 5:20 am 
Daniel CromptonOct 23, 2008 4:22 am 
Maxim DouninOct 23, 2008 4:48 am 
Daniel CromptonOct 23, 2008 5:00 am 
Maxim DouninOct 23, 2008 5:24 am 
Daniel CromptonOct 23, 2008 5:56 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:head requests and chunked transfer encodingActions...
From:Spil Games (lis@ruby-forum.com)
Date:Oct 1, 2008 2:04:56 am
List:ru.sysoev.nginx

Hi,

I ran into some problems with Curl doing HEAD requests on an Nginx server:

$ curl -I 'http://www.mydomain.com/test.php' HTTP/1.1 200 OK Server: nginx Date: Wed, 01 Oct 2008 09:01:16 GMT Content-Type: text/html Transfer-Encoding: chunked Connection: keep-alive

curl: (18) transfer closed with outstanding read data remaining

I think the problem occurs under the following circumstances:

- 'Content-Length' header not set (by PHP) - 'Transfer-Encoding: chunked' header set (by Nginx)

And I believe Nginx may be at fault because I believe it should send at least one empty chunk when claimed to do chunked transfer encoding.

Wouldn't it be better to not use chunked transfer encoding at all for HEAD requests?

-- Posted via http://www.ruby-forum.com/.