Re: [squid-users] just finished setting up squid 2.4 STABLE7 + Redhat 8 (kernel 2.4) and + IPTABLES v1.2.6a

Hello Henrik,

thank you very much,
i've just enabling the log_mime_hdrs.
i'll tell my clients to give it a try tommorow and check the log files.
because it's sunday now :P

thankyou again everyone

see u again

----- Original Message -----
From: "Henrik Nordstrom" <hno@squid-cache.org>
To: <inghau@perkom.co.id>; <squid-users@squid-cache.org>
Sent: Saturday, January 25, 2003 2:58 AM
Subject: Re: [squid-users] just finished setting up squid 2.4 STABLE7 +
Redhat 8 (kernel 2.4) and + IPTABLES v1.2.6a

> There is three main cases to why Squid does not cache all http
> request:
>
> a) The server has marked the reply as not cacheable. See the
> cacheability check engine (linked from Related Software).
>
> b) The client requests a fresh copy not from cache.
>
> c) The server did not provide any relevant expiry information, making
> Squid assume the object is dynamically created.
>
>
> For detailed analysis on what is your case, enable log_mime_hdrs, and
> then send a log with two requests
> 1. The first request, which supposedly should have made the obejct
> cached.
> 2. A second request, which supposedly should have been a HIT but which
> was a MISS:
>
> Regards
> Henrik
>
>
>
> On Saturday 25 January 2003 20.49, inghau@perkom.co.id wrote:
> > Hello everybody,
> >
> > i've just finished installing squid on my linux box, and it seems
> > to work for caching HTTP request for my betea tester clients.
> > Right now my next target it to cache the FTP request too,
> > because most of my clients using some update program to request the
> > data from main ftp server (just like when you update Norton Anti
> > Virus database file, but the "update" that my client's requesting
> > is very big abuot 70Mb/update that's why i need to cache it)
> > But as far as i understand squid cannot act as FTP transparent
> > proxy that's why the squid only accept traffic to destination port
> > 80. (please correct me if i'm wrong)
> >
> > Actually the program that my client's are using support http
> > request update too, but when i checked the log squid said like
> > this. as i understand that it always TCP_MISS and DIRECT, has
> > anyone can tell me what can i do to cache these request ?
> > is it easier to fix this or just use the other program like frox ?
> >
> > 1043383117.475 3878 192.168.10.34 TCP_MISS/200 361 GET
> > http://ftp.ibmlink.ibm.com/econfig/ECFXF_ACTIVE_DIR.CTL -
> > DIRECT/207.25.249.17 text/plain
> > 1043383129.853 12324 192.168.10.34 TCP_MISS/200 11871 GET
> > http://ftp.ibmlink.ibm.com/econfig/FXFDIR2/NMFD_SERVER_DEFAULT_CONT
> >ROL.SER - DIRECT/207.25.249.17 text/plain
> > 1043383148.619 12592 192.168.10.34 TCP_MISS/200 665 GET
> > http://ftp.ibmlink.ibm.com/econfig/FXFDIR2/STAGE/AP%20AS400/NMFD_SE
> >RVER_CRCT ABLE.SER - DIRECT/207.25.249.17 text/plain
> > 1043383154.746 6086 192.168.10.34 TCP_MISS/200 677 GET
> > http://ftp.ibmlink.ibm.com/econfig/FXFDIR2/STAGE/AP%20AS400%20SOFTW
> >ARE/NMFD_ SERVER_CRCTABLE.SER - DIRECT/207.25.249.17 text/plain
> > 1043383161.082 6323 192.168.10.34 TCP_MISS/200 679 GET
> > http://ftp.ibmlink.ibm.com/econfig/FXFDIR2/STAGE/AP%20RS6000%20SOFT
> >WARE/NMFD _SERVER_CRCTABLE.SER - DIRECT/207.25.249.17 text/plain
> > 1043383173.742 12646 192.168.10.34 TCP_MISS/200 669 GET
> > http://ftp.ibmlink.ibm.com/econfig/FXFDIR2/STAGE/AP%20RS6000/NMFD_S
> >ERVER_CRC TABLE.SER - DIRECT/207.25.249.17 text/plain
> >
> > Has anybody having the same problem like i do ?
> > Thank you very very much.
> >
> > Best Regards
> > inghau@perkom.co.id
> > Network Engineer
> > www.perkomonline.com
>
>
Received on Sat Jan 25 2003 - 22:51:07 MST