On 05/11/10 13:45, Nick Rathke wrote:
> Hi,
>
> I have been trying various configuration combination for days and
> reading the FAQ and the configuration documentation trying to get a
> basic web cache to work without much luck.
>
> I have a department web site that I need to cache on some local systems,
> I need to cache as much as possible to limit the bandwidth use. 90% of
> the content is video .mov | .mp4 | .jpg files that loop in a sequence of
> and over again which is why I don't want to have them download each time
> they play. There is also a live RSS feed in the page the does need to
> refresh all the time.
The caching properties of these types of files is best set by the web
server producing them. Squid can only play with the details is gets
given. It can't make up completely new ones in any safe way.
>
> I have included my configuration that I have now. The web "clients" are
> running openSUSE with squid 2.7.STABLE6-6.1
??? confusion.
You are talking above and below about *a* proxy with problems. The
nature of "clients" is not relevant.
Do you mean a linkage of:
clients-> proxy with problems -> server
or:
multiple proxies with same problems -> server
?
> from a 4GB USB drive that
> has about 800GB free, systems have 1GB or RAM ( which I have not gone to
> go above 30% used ).
>
> The store log seems to show media files with a "SWAPOUT" but when I look
> at the network activity it looks like firefox is still down loading them.
>
> The RSS is not update and is being cached ( which it shouldn't be ) Then
> the .mov file startes play the store state seems to move to "RELEASE"
I have yet to see a working RSS feed which permits caching for longer
than a small amount of minutes. Most RSS can safely be cached for a few
seconds to limit flooding.
You can plug public URLs into redbot.org to get a report of what a proxy
will do and why. Any problems detected there need to be fxed at the
source web server. Local proxy fixes will leave great amounts of
invisible-to-you breakage for real visitors.
Assuming it is a 2.7 config there is nothing badly wrong about it.
> reply_body_max_size 0 allow all
Remove the "allow all" part of the above line.
In 2.x the ACL are not supported. This limit applies globally.
Your maximum stored object size of 256 MB may affect some of the videos
being stored. The problem is more likely to be no-store/no-cache or bad
timestamps being sent by the web server though.
Amos
-- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.9 Beta testers wanted for 3.2.0.2Received on Fri Nov 05 2010 - 04:12:38 MDT
This archive was generated by hypermail 2.2.0 : Fri Nov 05 2010 - 12:00:01 MDT