Re: best practices on setting HTTP headers and status codes

seems we don't have a consensus on this as I was expecting :-)

I tested it with plone.app.caching and I see it will override the 
headers when selecting different configurations.

so, I think is fine to leave the handling of 304 on the package as 
configuring it with plone.app.caching is not trivial and it hurts no one.

thanks!

Héctor Velarde

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers