You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 21, 2023. It is now read-only.
From:
http://groups.google.com/group/mod-pagespeed-discuss/browse_thread/thread/2a909b
19159dfd37
>> [Thu Nov 04 14:29:39 2010] [error] [1104/142939:ERROR:net/instaweb/
util/google_message_handler.cc(54)] http://localhost/(PHP-generated
image request):1: Reached end of document without finding <body>
>>
>> I'm sure some of these could be fixed with some tweaking to the
configuration, but I thought I'd still put these in case it can be
helpful to the developers working on the module.
> Are you saying that you requested an image and it gave you this error
message? That's good to know. It means that it was parsing that image as an
html doc! I believe we choose which files to rewrite based on MIME type
reported by Apache, do you think there would be any reason that this would have
been reported as text/html or anything like that?
Thanks for your explanation of the error messages. The images are
generated in PHP and are loaded using a url ending in .php, but I set
the content-type HTTP header to image/png, so it shouldn't be an
issue.
Here are the response headers for one of the images that resulted in
the above error:
Date Fri, 05 Nov 2010 14:01:00 GMT
Server Apache/2.2.16 (Ubuntu)
X-Powered-By PHP/5.3.3-1ubuntu9.1
Last-Modified Thu, 28 Oct 2010 14:01:40 GMT
Content-Length 19548
Content-Disposition inline; filename="4.8_4896_7353x_4847_7305y.png"
Cache-Control max-age=7776000
Expires Thu, 03 Feb 2011 14:01:00 GMT
Content-Type image/png; charset=binary
Vary Accept-Encoding
Original issue reported on code.google.com by sligocki@google.com on 5 Nov 2010 at 3:32
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
sligocki@google.com
on 5 Nov 2010 at 3:32The text was updated successfully, but these errors were encountered: