nginx reports [upstream sent no valid HTTP/1.0 header] when used with varnish
joydeep.bakshi at netzrezepte.de
Tue Apr 22 08:45:26 UTC 2014
I have just checked and found nothing
# tcpdump -vv port 6082
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
On Tue, Apr 22, 2014 at 1:39 PM, Lukas Tribus <luky-37 at 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: 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: 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?
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx