Bug #527 still at large

[John Moser]

Issue #527 includes some quick and dirty code in a tarball to reproduce the issue, but hasn't been looked at or commented over.

To get an idea of this:

http://www.foxbaltimore.com/

versus

http://www.foxbaltimore.com/?PageSpeed=on&

Near as I can tell, it's lines like this in shtml that break it:

<!--#include virtual="/inc/header/" -->

Using lines like this instead unbreak it:

<!--#include virtual="/inc/header/index.shtml" -->

Any work-arounds that don't involve modifying several tens of millions of lines of shtml?  (We have about 1.5 million files here each ranging between 10 and 80 #include lines, probably half of which are affected)

[Joshua Marantz]

I followed up on the bug thread.  I still don't know how to reproduce locally.

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/6f31e296-2e21-43f9-9212-71cdde9da65c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Moser]

Thanks.  I think I forgot some instructions and a directive in the vhost.

It's just been a while and I have no idea why it does this or how to fix.  You'd think SSI would run first (an earlier bug covers this) and then mod_pagespeed would just parse the output, so what's happening doesn't make sense to me.