[squid-users] Transparent Squid Proxy Server

[Reet Vyas]

Thank you everyone for helping me to setup squid , Now its working but in
access.logs  I only see tcp_miss if m using same website. I mean squid is
not caching

Logs

43 192.168.0.198 TCP_MISS/200 384461 GET
http://www.horlicksquad.com/images/tc-pic.png - HIER_DIRECT/52.74.133.61
image/png
1433422076.988    309 192.168.0.198 TCP_MISS/200 38007 GET
http://www.horlicksquad.com/about-us - HIER_DIRECT/52.74.133.61 text/html
1433422077.188    224 192.168.0.198 TCP_MISS/200 17622 GET
http://www.horlicksquad.com/images/panel05.png - HIER_DIRECT/52.74.133.61
image/png
1433422077.226    140 192.168.0.198 TCP_MISS/200 13840 GET
http://www.horlicksquad.com/images/au-bg.png - HIER_DIRECT/52.74.133.61
image/png
1433422077.261    208 192.168.0.198 TCP_MISS/200 60858 GET
http://www.horlicksquad.com/images/sonny-horlicks-abtus.png - HIER_DIRECT/
52.74.133.61 image/png

How to check cache is working or not. I want to cache videos images css

On Thu, Jun 4, 2015 at 3:37 PM, Amos Jeffries <squid3 at treenet.co.nz> wrote:

> On 4/06/2015 6:43 p.m., Reet Vyas wrote:
> > Hi,
> >
> > I changed the iptables still no luck :( but I am using squid 3.3 only
> can I
> > didn't understand why you have configured 3129 ,3130 and 3128 port?
>
> Because due to historic (browser war politics) reasons there are three
> different protocol message syntax in HTTP/1.x - depending whether the
> traffic is on port 80 (HTTP origin), 443 (HTTPS origin), or 3128 (HTTP
> proxy).
>
>
> * Normal forward/explicit proxy traffic occurs on port 3128. Squid needs
> this port regardless of whether your main traffic use is on another port
> type, because some proxy responses will have URLs generated for embeded
> content to be fetched from the proxy itself.
>
> * NAT intercepted port 80 traffic needs to be delivered to a different
> proxy http_port with the "intercept" flag. The tutorials use 3129 to
> make it clear its not to be 3128, but it SHOULD be something random you
> make up that you can also have the firewall blocking connections
> directly to it by clients.
>
> * NAT intercepted port 443 traffic needs https_port directive (note the
> 's') which means another port number separate from the port 80 one.
>
>
> Amos
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150604/3c3f003d/attachment.html>