Welcome! Log In Create A New Profile

Advanced

Re: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

All files from this thread

File Name File Size   Posted by Date  
tcp6082-traffic.cap 4.5 KB open | download Joydeep Bakshi 04/22/2014 Read message
Joydeep Bakshi
April 22, 2014 04:46AM
Hello Lukas,

I have just checked and found nothing

# tcpdump -vv port 6082
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
bytes







On Tue, Apr 22, 2014 at 1:39 PM, Lukas Tribus <luky-37@hotmail.com> wrote:

> > Hello all,
> >
> > My setting works well through nginx->apache but not through
> > nginx->varnish->apache
> >
> > apache is configured to listen to port 8080 . when nginx uses
> >
> > proxy_pass http://127.0.0.1:8080
> >
> > the sites are running fine.
> >
> > If I introduce varnish after nginx by [proxy_pass
> > http://127.0.0.1:6082] the nginx starts throwing following error and
> > browser also shows "Zero Sized Reply"
> >
> >
> > [error] 17147#0: *207 upstream sent no valid HTTP/1.0 header while
> > reading response header from upstream
> >
> > and /var/log/messages shows
> >
> > varnishd[16984]: CLI telnet 127.0.0.1 42212 127.0.0.1 6082 Wr 101
> > Unknown request.#012Type 'help' for more info.#012all commands are in
> > lower-case.
> >
> > varnishd[16984]: CLI telnet 127.0.0.1 42212 127.0.0.1 6082 Rd
> > Cache-Control: max-age=0
>
> Can you capture the tcp 6082 traffic and post the entire HTTP conversation?
>
>
>
> Lukas
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Joydeep Bakshi April 22, 2014 03:26AM

RE: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Lukas Tribus April 22, 2014 04:12AM

Re: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Joydeep Bakshi April 22, 2014 04:46AM

RE: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Lukas Tribus April 22, 2014 04:58AM

Re: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Joydeep Bakshi April 22, 2014 05:06AM

RE: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Lukas Tribus April 22, 2014 05:34AM

Re: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Maxim Dounin April 22, 2014 05:36AM

Re: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish Attachments

Joydeep Bakshi April 22, 2014 06:02AM

Re: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Maxim Dounin April 22, 2014 06:22AM

RE: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Lukas Tribus April 22, 2014 06:24AM

Re: nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish

Joydeep Bakshi April 22, 2014 09:10AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 218
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready