Mailing List Archive: hiding varnish headers from requests

Hello, list.

I have set like below at varnishd 1.1.2 and works well.
But like below just connect to port 80 and quit, we can see all headers.

Any idea?

# telnet 127.0.0.1 80Trying 127.0.0.1...Connected to 127.0.0.1.Escape character is '^]'.quit

HTTP/1.0 400 Bad RequestServer: VarnishRetry-After: 0Content-Type: text/html; charset=utf-8Content-Length: 428Date: Mon, 07 Jan 2008 11:42:33 GMTX-Varnish: 1556702737Age: nanVia: 1.1 varnishConnection: keep-alive

Thanks

Date: Thu, 13 Dec 2007 16:23:02 -0800From: jbittman at chewcorp.comTo: dwetzel at nerim.netSubject: Re: hiding varnish headers from requestsCC: varnish-misc at projects.linpro.noEdit your vcl file and modify deliver like so.sub vcl_deliver { remove resp.http.X-Varnish; remove resp.http.Via;}
On 11/2/07, Damien Wetzel <dwetzel at nerim.net> wrote:
Hello,I wondered if there is a way to prevent Varnish fromputing headers like :X-varnishVia: 1.1 varnishin its responses to clients.thanks,--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Damien WETZEL (ATANAR TECHNOLOGIES) ("`-/")_.-'"``-._http://www.atanar.com . . `; -._ )-;-,_`) (v_,)' _ )`-.\ ``-' Phone:+33 6 62 29 61 77 _.- _..-_/ / ((.'- So much to do, so little time - ((,.-' ((,/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~_______________________________________________ varnish-misc mailing listvarnish-misc at projects.linpro.nohttp://projects.linpro.no/mailman/listinfo/varnish-misc -- Jobe BittmanChief Network ArchitectZenGarden, Inc.(858) 200-6099
_________________________________________________________________
MSN ???? ??? ??, Windows Live Messenger!
http://windowslive.msn.co.kr/wlm/messenger/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.linpro.no/pipermail/varnish-misc/attachments/20080107/c8bf5183/attachment.htm

MontyRee <chulmin2 at hotmail.com> writes:

> Hello, list.
>
> I have set like below at varnishd 1.1.2 and works well. But like
> below just connect to port 80 and quit, we can see all headers.
>
> Any idea?

Your "quit" request, which is not a valid HTTP request, causes Varnish
to respond with an error message.

This error message contains the response "HTTP/1.0 400 Bad Request",
as well as a set of headers describing the format of the error
message, and information that can be used to find the cause of the
error.

Your example shows that you are using telnet to connect to Varnish.
The proper way to exit this client is not to type "quit", but rather
with the escape character '^]', followed by the command "close", which
may also be abbreviated to "c". For more information, see your
system's telnet(1) man page.

--
Stig Sandbeck Mathisen, Linpro