Post Reply 
Content-Length header problem
Dec. 21, 2011, 04:45 AM (This post was last modified: Dec. 21, 2011 04:12 PM by sh8an.)
Post: #1
Content-Length header problem
Hi all,

Have a strange issue here.
First the normal setup.
Browser->Handycache->Proxo->Net
If some image is opened the Content-Length header is transferred from Proxo as the last one in the headers block and Handycache for some reason doesn't see it. If I click the Bypass All button in Proxo then everything is OK, the Content-Length header is in the middle of the block and Handycache works with it fine.
Browser->Fiddler->Handycache->Proxo->Net
Fiddler interprets the same header block OK
How do i make it not the last one with Proxo? Maybe add some made up header?
Thanks in advance.

ps
the link used for checking - http://i31.fastpic.ru/big/2011/1220/ce/f...a330ce.jpg


Update
After a bit of investigation noticed that this happens with jpg and png images and not with gifs. some header info below
Proxo headers
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 21 Dec 2011 15:50:29 GMT
Content-Type: image/jpeg; PrxMsg: Filter Image
Content-Length: 91656
Last-Modified: Tue, 20 Dec 2011 09:24:39 GMT
Connection: keep-alive
Accept-Ranges: bytes
Cache-Control: no-store, no-cache, max-age=0
Pragma: no-cache
|.*.URL-ID: (252) http://i29.fastpic.ru/big/2011/1220/87/d...999e87.jpg

Handycache headers
21.12.11 20:50:24,014 # 1927 <<< URL: http://i29.fastpic.ru/big/2011/1220/87/d...999e87.jpg
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 21 Dec 2011 15:50:29 GMT
Content-Type: image/jpeg; PrxMsg: Filter Image
Last-Modified: Wed, 21 Dec 2011 15:50:23 GMT
Accept-Ranges: bytes
Cache-Control: no-store, no-cache, max-age=0
Pragma: no-cache
|.*.URL-ID: (252) http://i29.fastpic.ru/big/2011/1220/87/d...999e87.jpg
Transfer-Encoding: chunked
Connection: keep-alive

Fiddler headers
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 21 Dec 2011 15:50:29 GMT
Content-Type: image/jpeg; PrxMsg: Filter Image
Last-Modified: Wed, 21 Dec 2011 15:50:23 GMT
Accept-Ranges: bytes
Cache-Control: no-store, no-cache, max-age=0
Pragma: no-cache
|.*.URL-ID: (252) http://i29.fastpic.ru/big/2011/1220/87/d...999e87.jpg
Connection: keep-alive
Content-Length: 91656

So Connection and Content-Length seem to be reordered
Took out HandyCache so chain is Fiddler->Proxo and here are the headers from Fiddler
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 21 Dec 2011 16:08:09 GMT
Content-Type: image/jpeg; PrxMsg: Filter Image
Last-Modified: Tue, 20 Dec 2011 09:24:39 GMT
Accept-Ranges: bytes
Cache-Control: no-store, no-cache, max-age=0
Pragma: no-cache
|.*.URL-ID: (304) http://i29.fastpic.ru/big/2011/1220/87/d...999e87.jpg
Content-Length: 91656

So it is definitely Proxo changing the order. Can anyone share an insight on reordering the headers please?
Add Thank You Quote this message in a reply
Post Reply 


Messages In This Thread
Content-Length header problem - sh8an - Dec. 21, 2011 04:45 AM
RE: Content-Length header problem - JJoe - Dec. 21, 2011, 07:20 PM
RE: Content-Length header problem - sh8an - Dec. 22, 2011, 11:16 AM
RE: Content-Length header problem - JJoe - Dec. 22, 2011, 07:26 PM
RE: Content-Length header problem - sh8an - Dec. 23, 2011, 04:36 AM
RE: Content-Length header problem - JJoe - Dec. 23, 2011, 04:45 AM

Forum Jump: