Thank you for your response, Eliezer.
I added the logformat command that you suggested. I needed to modify it slightly, since I'm running squid 3.1 (I changed <a to <A and removed %>eui). An example of what I am seeing in /var/log/squid/access.log is:
1457630282.410 490 172.31.169.175 TCP_MISS/200 4621 GET https://<server>/tw4/index.php/Two - FIRST_UP_PARENT/127.0.0.1 text/html Q-CC: "max-age=0" "max-age=0" Q-P: "-" "-" REP-CC: "s-maxage=18000, must-revalidate, max-age=0" REP-EXP: "-" VARY: "-"
I am testing from a desktop browser (Chrome and IE). I am entering the page address directly rather than doing a browser refresh. I am watching /var/log/squid/access.log and /var/log/httpd/access.log to see what requests squid and apache are receiving.
Thank you,
Cindy
Hey Cindy, I do not have too much experience with MediaWIKI but I ran some test on it in the past for both caching and other things. I am using this logformat to detect couple things that are related to caching: logformat cache_headers %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt Q-CC: "%{Cache-Control}>h" "%{Cache-Control}>ha" Q-P: "%{Pragma}>h" "%{Pragma}>ha" REP-CC: "%{Cache-Control}<h" REP-EXP: "%{Expires}<h" VARY: "%{Vary}<h" %>eui access_log daemon:/var/log/squid/access.log cache_headers The headers: Cache-Control: s-maxage=18000, must-revalidate, max-age=0 clearly states that the response should not 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 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 <external ip>:443 for HTTPS > requests and forwards them to Apache on port 8080 > > https_port <external ip>:443 cert=<path to cert> key=<path to key> > defaultsite=<server name> vhost > cache_peer 127.0.0.1 parent 8080 no-query originserver login=PASS > > * Squid also listens on 127.0.0.1:80 <http://127.0.0.1:80> for PURGE > requests from MediaWiki because I could not figure out how to > configure MediaWiki to send PURGE requests with HTTPS > > http_port 127.0.0.1:80 <http://127.0.0.1:80> defaultsite=<server name> vhost > > * Apache is listening on 127.0.0.1:8080 <http://127.0.0.1:8080> for > requests from Squid > * Apache is also listening on <external ip>:80 which is set up as a > permanent redirect to HTTPS > * MediaWiki is configured as follows: > > $wgUseSquid = true; > $wgSquidServers = array('127.0.0.1'); // this is where PURGE requests > are sent > $wgSquidServersNoPurge = array('<external ip>'); > > GET requests are being received by MediaWiki with Cache-Control: > max-age=0 in the headers. The response sent by MediaWiki includes the > following headers: > > Cache-Control: s-maxage=18000, must-revalidate, max-age=0 > X-Cache: MISS from <server name> > X-Cache-Lookup: HIT from <server name>:80 > > I am suspicious why the last line says port 80 rather than 8080, but I'm > not sure if that is relevant. > > Please let me know if there is an more relevant information that will > help to troubleshoot this. Thank you in advance for your assistance! > > Cindy >
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
