nginx adds extra chunked header while proxying anytermd

san nonexist at gmail.com
Fri May 9 13:39:39 MSD 2008


Thanks for your reply. Could you give me a
hint  that I can modify the nginx source code to let nginx outputs the
original data?


On 5/9/08, Igor Sysoev <is at rambler-co.ru> wrote:
>
> On Fri, May 09, 2008 at 08:55:46AM +0800, san wrote:
>
> > I have a problem while using nginx to proxy anytermd. anytermd is a
> simple
> > web server which always outputs chunked
> > data. The following is the data that nginx gave to me:
> >
> > HTTP/1.1 200 OK
> > Server: nginx/0.5.36
> > Date: Fri, 09 May 2008 00:30:37 GMT
> > Content-Type: text/html
> > Transfer-Encoding: chunked
> > Connection: close
> > Transfer-Encoding: chunked
> >
> > 75f
> > 753
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> > ......
> > 0
> >
> >
> > 0
> >
> > I saw the doc said that nginx talks http/1.0 to the backend server.How
> can I
> > let the nginx outputing the original data?
>
>
> It's bug in anytermd. It must not send a chunked response for http/1.0
> request:
> a http/1.0 client does not understand this encoding.
>
>
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080509/974f13f4/attachment.html>


More information about the nginx mailing list