On Sun, Jun 5, 2011 at 21:37, Joshua Marantz jmara...@google.com wrote:
Does Magento actually vary the content of CSS JS based on user-agent? Or
does it only vary the content of HTML?
I don't know. I'm by no means a Magento expert, I only run into it
from time to time. That site I broke? That
On Sun, Jun 5, 2011 at 13:42, Joshua Marantz jmara...@google.com wrote:
This is a case where the content varies based on user-agent. The
recommendation on the mod_deflate doc page is add vary:user-agent for any
non-image. Can you think of a case where the absence of a vary:user-agent
header
Thanks for the feedback, Ben! You are omniscient in the ways of Apache.
I'll try to lobby for an update to the mod_deflate page.
Your concerns about Magento are interesting -- my impression from our forums
and Twitter is that mod_pagespeed is successfully accelerating many Magento
sites now,
This encourages all site owners to add Vary:User-Agent to all css and js
files, whether they actually vary in content or not.
Does anyone know the history of this recommendation? Surely that is an
inappropriate recommendation for mod_deflate. Vary:Accept-Encoding make
sense in the context
On Sat, Jun 4, 2011 at 21:26, Joshua Marantz jmara...@google.com wrote:
I think what we'd do is basically let mod_pagespeed ignore Vary:User-Agent
if we saw that it was inserted per this exact pattern. This would, to be
This seems like a stupendously bad idea. Warn about it in your docs,
It was with some reluctance that I brought this up. It occurs to me that
this idea propagates the sort of spec violations that led to this issue
(inappropriate user of Vary:User-Agent) in the first place. However, I'm
trying to figure out how to improve compliance to support legitimate uses of
On Sun, Jun 5, 2011 at 00:34, Joshua Marantz jmara...@google.com wrote:
It was with some reluctance that I brought this up. It occurs to me that
this idea propagates the sort of spec violations that led to this issue
(inappropriate user of Vary:User-Agent) in the first place. However, I'm
