Hello, I think that more on:
- Cherokee version. - Cherokee configuration used. would be interesting to try to help you. On Fri, Mar 18, 2011 at 6:14 PM, saturne <[email protected]> wrote: > Hello, > > During lot of days, I searched a server / system who is synchronous with my > cgi. All servers put into a cache memory or file the bytes I sent. And > Cherokee is my solution, I'm happy ;). > > I explain my problem, and why I need to remove headers. > On light, I develop a cgi script (C) who get some bytes from files, and > fwrite to stdout to the client. > The client can download, resume, or streaming the file. Good.... > > When a client resume (or stream), he sent a header "Range" to get a part of > file, ok.. > > When a client resume (or stream), I sent the header (the firt) : > HTTP/1.1 206 Partial Content > > So, on light, if I resume a file, light do not sent any header, because my > cgi script sent (here 7Go): > HTTP/1.0 206 Partial Content > Accept-Ranges: bytes > Content-Range: bytes 0-7569935360/7569935361 > Content-Length: 7569935361 > > On cherokee, big problem! He sent: > HTTP/1.0 200 OK > Connection: Keep-Alive > Keep-Alive: timeout=15 > Date: Fri, 18 Mar 2011 16:48:30 GMT > Server: Cherokee > > And after, my header! HTTP/1.1 206 Partial Content > > The problem is about the First header! (after the second, Cherokee sent a > header, no problem) > > So, it is a bug ?, or, it is possible, IF a script sent a HTTP/1.X header, > Cherokee understand to NOT sent this header! > > Thanks a lot > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > -- Saludos: Antonio Pérez _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
