Hi, Polipo intentionally ignores [1] weak ETags. Why? The very concept of a weak entity tag [2] exists because some entity tags are unreliable for concurrency control (aka the "lost update" problem) but still useful for cache validation.
What's more, Polipo removes weak ETags from responses [3]. Is this intentional? This doesn't seem right. Even if a weak ETag is (in theory) unusable for conditional PUT/DELETE, it is generic metadata that may still be interesting to the client for any reasons (logging, for instance). This isn't a problem for me, I'm just curious. [1] https://github.com/jech/polipo/blob/882029b/http_parse.c#L1039 [2] http://tools.ietf.org/html/rfc7232#section-2.1 [3] https://gist.github.com/vfaronov/7956776b66d3f836dd0f -- Vasiliy ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
