For example I searched something in "https://www.google.com"; and access.log is as below: 1390982819.881 651 10.1.116.50 TCP_MISS/200 855 POST http://clients1.google.com/ocsp - HIER_DIRECT/216.239.32.20 application/ocsp-response 1390982820.131 655 10.1.116.50 TCP_MISS/200 855 POST http://clients1.google.com/ocsp - HIER_DIRECT/216.239.32.20 application/ocsp-response 1390982820.869 981 10.1.116.50 TCP_MISS/200 1878 POST http://gtglobal-ocsp.geotrust.com/ - HIER_DIRECT/23.59.139.27 application/ocsp-response 1390982821.129 997 10.1.116.50 TCP_MISS/200 1878 POST http://gtglobal-ocsp.geotrust.com/ - HIER_DIRECT/23.59.139.27 application/ocsp-response 1390982830.019 671 10.1.116.50 TCP_MISS/200 855 POST http://clients1.google.com/ocsp - HIER_DIRECT/216.239.32.20 application/ocsp-response 1390982830.196 676 10.1.116.50 TCP_MISS/200 855 POST http://clients1.google.com/ocsp - HIER_DIRECT/216.239.32.20 application/ocsp-response 1390982830.266 665 10.1.116.50 TCP_MISS/200 855 POST http://clients1.google.com/ocsp - HIER_DIRECT/216.239.32.20 application/ocsp-response 1390982830.440 669 10.1.116.50 TCP_MISS/200 855 POST http://clients1.google.com/ocsp - HIER_DIRECT/216.239.32.20 application/ocsp-response > On 29/01/2014 7:28 p.m., m.shahverdi@xxxxxxxxxxxx wrote: >> Thanks a lot, but I'm running a squid on another system that is passing >> https requests and logging them in "access.log" perfectly! I use same >> config file for both. >> > > Logging them as what exactly? (the full exact access.log lines please). > > Are you really sure that is Squid on the other machine? > Because HTTPS has *never* been valid on port-80 which is what > "http_port ... tproxy" configures Squid to receive. > > Amos >
