Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Firebug errors (404s) when mousing over images rewritten with mod_pagespeed enabled. #53

GoogleCodeExporter opened this issue Apr 6, 2015 · 6 comments


Copy link

What steps will reproduce the problem?
1. Installed on Server
2. Loaded Page
3. Next time, main image was broken

What is the expected output? What do you see instead?
Expected to see an image.  After the first time the image loaded, the next time 
(and all times after that) appeared a broken image.

What version of the product are you using (please check X-Mod-Pagespeed

On what operating system?
Ubuntu 9.10 server 64bit

Which version of Apache?

Which MPM?

Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.

Had to disable the module.

Here's a page -- it only did it with the main/big image.

Original issue reported on by on 9 Nov 2010 at 2:03

Copy link

Quick update on this: using a local mirror of this site, the main image looks 

However, as I drag my mouse over the 3 images on the lower left "Email this 
Photo to a Friend" etc, we get red 404s in Firebug.  So there is still a bug 
with this site.

Original comment by on 20 Nov 2010 at 12:19

Copy link

Summary was: Images only load once, then 

One of the 404s is

This does not occur when mod_pagespeed is off.  It looks like it might be a 
relative path issue from Javascript or CSS.

Original comment by on 20 Nov 2010 at 12:22

  • Changed title: Firebug errors (404s) when mousing over images rewritten with mod_pagespeed enabled.

Copy link

It'd be worth seeing if wget still fetches the images.  This sounds a
bit like what I was seeing with failing HEAD requests from Firefox.

Original comment by on 22 Nov 2010 at 3:09

Copy link

Installed latest release tonight, but still had images disappearing after the 
first time the page was viewed.  

Seemed to be less disappearing than before.

Original comment by on 24 Nov 2010 at 4:19

Copy link

With the latest version of the code in SVN the errors no longer pop up.  The 
fix for this is *not* in, the latest binary release, but *is* in 
SVN trunk.

We will also put a reference to this bug in the announcement for the next 
binary release.

Original comment by on 21 Dec 2010 at 10:50

  • Changed state: Fixed
  • Added labels: release-note

Copy link

Just installed on my server.  It works now.  Thx.

Original comment by on 24 Dec 2010 at 5:15

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

1 participant