>
> Ah. That being an old version may be part of your problem. 3.1 only
> supports ~60% of HTTP/1.1 requirements.
>
I have spent some time trying to build 3.5.15 from source and install it on
Red Hat, hoping it would resolve the caching issue. It builds fine, but I'm
having permission issues with
>
> > I added the logformat command that you suggested. I needed to modify it
> > slightly, since I'm running squid 3.1 (I changed > %>eui). An example of what I am seeing in /var/log/squid/access.log is:
>
> The 'eui' change is okay, but to ensure the traffic is flowing through
> the correct rout
ot be cached by the client but
> supposed to be cached by a surrogate.
> How do you test caching? wget? curl? script? netcat? a desktop browser?
>
> Eliezer
>
> On 10/03/2016 16:22, Cindy Cicalese wrote:
> >* I am using Squid for caching with Apache and MediaWiki over HTTPS on
I am using Squid for caching with Apache and MediaWiki over HTTPS only.
Unfortunately, no pages are being cached; each request is being sent from
Squid to Apache. I would appreciate help figuring out how to get caching to
work.
My configuration is as follows:
- Squid is configured to listen on
