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.
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
