Re: [twsocket] HTTP protocol issue

2010-05-23 Thread Fastream Technologies
Hi again, I think I found a solution: when GZip is in place, I remove the content-range response header line and just use content-length and content-encoding. Seems to work... Regards, SZ On Sun, May 23, 2010 at 4:27 PM, Fastream Technologies wrote: > Oops, I mixed the "Content-range" response

Re: [twsocket] HTTP protocol issue

2010-05-23 Thread Fastream Technologies
Oops, I mixed the "Content-range" response header with "Range" request header. Other than that the issue still remains. On Sun, May 23, 2010 at 4:24 PM, Fastream Technologies wrote: > Hello, > > I have a question: Let's say the request has Content-Range: 50-100 for a > file of length = 100. Now w

[twsocket] HTTP protocol issue

2010-05-23 Thread Fastream Technologies
Hello, I have a question: Let's say the request has Content-Range: 50-100 for a file of length = 100. Now we want to return the Range: 50-100/100 as GZipped. the last 50 bytes of the file is compressed to 40 bytes. How should one construct the response header? Range? Content-length? Regards, SZ