New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

false warning: end of document without finding body #73

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Apr 6, 2015

This occurs on many web pages.  The cause appears to be various resources -- 
images and javascript is what I've seen -- that are served by mod_pagespeed, 
but which come into mod_pagespeed in the filter chain with a content_type of 
text/html.  These are likely being fixed up by mod_headers, but mod_pagespeed 
is trying to process them as if they were HTML.

One candidate solution has been found where the first bytes of any HTML 
streaming through mod_pagespeed are scanned and, if not looking like HTML, then 
mod_pagespeed just passes them through directly without processing.  This 
eliminates those messages.

Another possible solution is to put mod_pagespeed *after* mod_headers which 
might be a better way of achieving the same objective.  We'd need to check that 
we left the headers in the correct state (content-length in particular comes to 
mind).  But I'm not sure how that would play with mod_deflate, which we 
definitely want to run after mod_pagespeed.


Original issue reported on code.google.com by jmara...@google.com on 12 Nov 2010 at 1:47

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 13 Nov 2010 at 12:46

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment