nginx as reverse proxy, returns garbage symbols

[Camilo Aguilar]

it means that I should not apply this patch:
http://www.ruby-forum.com/attachment/1891/patch.chunkedfrom:
http://www.ruby-forum.com/topic/152435
??

Regards,

Camilo Aguilar



On Wed, Sep 23, 2009 at 12:01 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Wed, Sep 23, 2009 at 11:45:09AM -0500, Camilo Aguilar wrote:
>
> > Hi everyone,
> > I am trying to use nginx as a reverse proxy and I am getting garbage
> symbols
> > in my json responses:
> >
> > 6a
> >
> {"codedField":[{"code":"01","name":"Dpto01"},{"code":"02","name":"Dpto02"},{"code":"03","name":"Dpto03"}]}
> > 0
> >
> >
> > I have tried with and without gzip and happens the same.
> >
> > My backend responses are well formed json and then I think that it should
> be
> > a nginx issue.
>
> Looks like your backend returns Transfer-Encoding: chunked to
> HTTP/1.0 requests (behaviour explicitly forbidden by RFC2616).
>
> Fixing backend should help.
>
> Maxim Dounin
>
>
> >
> > Can anybody help me please ?
> >
> > Regards,
> >
> > Camilo Aguilar
> >
> >
> >
> >
> >
> > --
> >   There are two ways of constructing a software design: One way is to
> make
> > it so simple that there are obviously no deficiencies, and the other way
> is
> > to make it so complicated that there are no obvious deficiencies. The
> first
> > method is far more difficult.  -C. A. R. Hoare
> >
> >   Any fool can write code that a computer can understand. Good
> programmers
> > write code that humans can understand. - Martin Fowler
>
>


-- 
  There are two ways of constructing a software design: One way is to make
it so simple that there are obviously no deficiencies, and the other way is
to make it so complicated that there are no obvious deficiencies. The first
method is far more difficult.  -C. A. R. Hoare

  Any fool can write code that a computer can understand. Good programmers
write code that humans can understand. - Martin Fowler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090923/18025192/attachment.html>