your mail

[Pritam Chavan]

Hi Maxim,

First of all thanks for your reply. 

I have checked my backend system It is working fine. If I hit same url
without nginx reverse proxy its giving proper output.
Example: For following configuration

location /bsg/ltp/live/$arg_name/$arg_name {
        proxy_pass http://localhost:8041;
    }

If I hit above url without nginx reverse proxy then its giving proper
output.

Thanks & Regards,
Pritam Chavan. 



Pritam Chavan
-----------------------------------------------------------------------------------------------------------------------------------------------
Disclaimer: This e-mail message may contain confidential, proprietary or legally privileged information. It should not be used by anyone who is not the original intended recipient. If you have erroneously received this message, please delete it immediately and notify the sender. http://www.edelweissfin.com/Portals/0/documents/miscellaneous/Disclaimer.pdf

-----Original Message-----
From: nginx [mailto:nginx-bounces at nginx.org] On Behalf Of Maxim Dounin
Sent: 26 February 2018 18:35
To: nginx at nginx.org
Subject: Re: your mail

Hello!

On Mon, Feb 26, 2018 at 12:35:15PM +0530, pritam chavan wrote:

> Hi All,
> 
> I am using open source NGINX as reverse proxy. There are certain URL 
> which have URL parameters.
> 
> I am getting following error while accessing this URL.
> 
> 2018/02/22 15:11:08 [error] 1606#0: *21 upstream sent invalid chunked 
> response while reading upstream, client: 10.109.1.4, server:
> XXX.XXXXXXXX.com, request: "GET /bsg/scrips HTTP/1.1", upstream: "
> http://127.0.0.1:8042/bsg/scrips", host: "XXX.XXXXXXXX.com:8030"
> 
> 2018/02/22 15:11:47 [error] 1606#0: *24 upstream sent invalid chunked 
> response while reading upstream, client: 10.109.1.4, server:
> XXX.XXXXXXXX.com, request: "GET /bsg/scrips HTTP/1.1", upstream: "
> http://127.0.0.1:8042/bsg/scrips", host: "XXX.XXXXXXXX.com:8030"

The message suggests the backend is broken and returns an invalid response
with broken chunked transfer encoding.  Check your backend.

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx