varnish reports [CLI telnet 127.0.0.1 42212 127.0.0.1 6082 Wr 101 Unknown request]

[Dridi Boukelmoune]

On Tue, Apr 22, 2014 at 10:04 AM, Joydeep Bakshi
<joydeep.bakshi at netzrezepte.de> 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"

Hi,

Varnish listens to the port 6081 by default for HTTP. The port 6082 is
the default port for the process administration (eg. varnishadm).

Cheers,
Dridi

> [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
>
> obviously varnish is configured to listen to apache
>
> backend default {
>         .host = "127.0.0.1";
>         .port = "8080";
> }
>
> Can anyone please suggest the possible reason which is causing the problem ?
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc