Following https://github.com/jech/polipo/issues/52
In some case, it's pretty useful while clearly off-standard, to force caching disregarding HTTP headers: broken, misconfigured-server, testing purposes (¹) An example: user-agent send a request (with keep-alive) server replies: > Cache-Control: no-cache, no-store, must-revalidate > Etag: <buggy-etag> > Expire: <in the past> Such requests won't be cached by polipo (relaxTransparency = true, mindlesslyCacheVary = true, cacheIsShared = false) Adding to this the ability to filter by mime-type or server-URL pattern would be a great bonus (and not only for off-standard cases) - Is it planned? - If no, would a patch implementing at least the "catch-all" part be accepted? Best regards ¹ Adding that when it comes to SSL, standalone proxies like Polipo are really the best place to manage file inspection (better than both browser-based developper extensions and tcpdump-like applications) ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
