Re: [squid-users] Reverse HTTPs proxy caching the content

Hello,

please configure your mailer to wrap lines below 80 characters per
line.
72 to 75 is usually OK.

Thank you.

On 20.10.11 15:36, Brueck Timm Wolfgang wrote:
>my intention was to use squid as an https-cache meaning that it should
> split https-sessions to be able to read and to cache the web content.
> (client <-https1-> proxy <-https2-> web server) Therefore, I
> configured squid as a reverse https-proxy.

Note that a "reverse proxy" does NOT mean that it accepts HTTPS
connections. The "reverse proxy" sits in front of HTTP server and
processes incoming requests for the server.

yes, reverse proxy can accept SSL connections, but that's a bit
different thing.

> The client receives the web-content from the web-server when I use
> the address of the proxy as destination. I would say everything
> works fine. However, when I look at the network traces I see that
> proxy responses to the client requests but it also retrieves the web
> content from the server. But using the CGI-interface the proxy
> reports IPcache hits. Is this a common behavior? Is there a
> possibility to configure squid in a way that it only should retrieve
> the web-content from the server when it is expired?

squid fetched content from server every time it is needed. Squid (by
default) won't cache something that is marked as non-cacheable.
If you want to offload your HTTP server by a proxy, the HTTP content
must be cacheable.

While you can workaround this at squid's side, configuring squid to
ignore some informations that say content is to be refreshed, the real
solution lies at server's side - make the content cacheable.

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -- Benjamin Franklin, 1759