Jason Spegal wrote:
> I was able to cache Pandora by compiling with --enable-http-violations
> and using a refresh_pattern to cache everything regardless. This however
> broke everything by preventing proper refreshing of any site. If it
> could be worked where violations only happened as directly specified in
> the configuration it would be a workable solution. I did some testing
> and I could not confirm that it was anything in the configuration file
> itself that was causing the issue. I wouldn't recommend using this as such.
>
Which indicates that there are fine tuning possible to cache just
Pandora. Find yoursef one of the Pandora URLs in your access.log and
take a visit to www.redbot.org or the ircache.org cacheability engine.
Amos
>
> Henrik Nordstrom wrote:
>> lör 2009-07-25 klockan 12:05 -0600 skrev Brett Glass:
>>
>>> One of the largest consumers of our HTTP bandwidth is Pandora, the
>>> free music service. Unfortunately, Pandora marks its streams as
>>> non-cacheable and also puts question marks in the URLs, which is a
>>> huge waste of bandwidth. How can this be overridden?
>>>
>>
>> The questionmark can be ignored. See the "cache" directive. But if there
>> is other parameters behind there (normally not logged) that just may not
>> help..
>>
>> Regarding non-cacheable.. most crap can be overridden by
>> refresh_pattern.
>>
>> But, if it's a streaming service (I know nothing about Pandora) then you
>> are quite likely out of luck.
>>
>> Regards
>> Henrik
>>
>>
>
-- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16 Current Beta Squid 3.1.0.10 or 3.1.0.11Received on Sun Jul 26 2009 - 01:33:26 MDT
This archive was generated by hypermail 2.2.0 : Sun Jul 26 2009 - 12:00:04 MDT