-
Notifications
You must be signed in to change notification settings - Fork 158
Apache2: /mod_pagespeed_beacon returns 404 #1291
Comments
what does your error or access logs say about the mod_pagespeed_statistics urls that are being requested and 404d? |
error.log:
It seems that the path is not handled by mod_pagespeed at all.
|
Hi,
Apache error and access logs agree that there is a 404 on that URL; however, the pagespeed-admin and pagespeed-global-admin pages work fine.
Beacon page is included like this:
|
When people change the beacon url, they probably mean to send the timings send by the instrumentation to another server for processing. Any discovered data we need for optimizing should be echoed back to the server that injected the beacon (critical images, css). #1291
When people change the beacon url, they probably mean to send the timings send by the instrumentation to another server for processing. Any discovered data we need for optimizing should be echoed back to the server that injected the beacon (critical images, css). #1291
When people change the beacon url, they probably mean to send the timings send by the instrumentation to another server for processing. Any discovered data we need for optimizing should be echoed back to the server that injected the beacon (critical images, css). #1291
I've been looking into the code that wires up the beacons pretty closely (see #1375) and tested a couple of things in light of this issue. |
In your posted configuration, the line: "RewriteEngine Off" is a misconfiguration (all three of "RewriteEngine Off" are misconfiguration), and adding it to your system will not change any system behavior. More importantly, the default value of “RewriteEngine" is already an "off", so adding “RewriteEngine Off" is quite unnecessary and it may cause confusion to users. Since herein there is no "RewriteRule", deleting “RewriteEngine Off” would be ideal. Related Apache source code snippet:
|
Hi there,
i've recently changed my setup from nginx to apache2 and can't get the Pagespeed-Beacon to work there. The request to the beacon always returns a 404 Status-Code. I'm using ProxyHTMLMeta to replace meta tags with the http-equiv-attribute that pagespeed ignores, but the problem does not seem related to that as the problem persits even if i disable ProxyHTMLMeta... Using the default-path (/mod_pagespeed_beacon) does not work also.
Is this a bug or am i doing something wrong?
Kind regards
Argelbargel
OS: Debian Jessie 8.21
Apache-Version: 2.4.20
Mod-Pagespeed-Version: 1.9.32.14-0
Apache-Configuration:
The text was updated successfully, but these errors were encountered: