Restarting polipo, purging its disk cache (polipo -x) and forcefully reloading does not help (in Firefox). With Google Chrome forcefully reloading helps however, and fixes the cache?!
This may be related to the order in which the browsers fetch the resources, and how polipo handles them (regarding pipelining etc).
I've started seeing the following error with SourceForge.net pages since switching to polipo yesterday:
The log (with logLevel=0xff):
My config:
I've tried adding these settings (and restarted polipo), but without luck:
Restarting polipo, purging its disk cache (
polipo -x
) and forcefully reloading does not help (in Firefox). With Google Chrome forcefully reloading helps however, and fixes the cache?!This may be related to the order in which the browsers fetch the resources, and how polipo handles them (regarding pipelining etc).
Wiping polipo's diskcache altogether (after stopping it) helps.
It appears to be related/caused by a JavaScript error, because some resource is gzipped, but the headers do not say so:
The file in polipo's disk cache (a.fsdn.com/+pdEifTwTC6+549yOVD+3g==) looks as follows:
See issue #43 for more investigation into this particular resource.
I am using polipo from Git (@e40fbbe7).
Could this be causes by pipelining or something similar, where polipo receives the content gzipped, although it's not when requested alone?!