-
Notifications
You must be signed in to change notification settings - Fork 361
StaticAssetPrefix not working #705
Comments
Could you paste the error you're getting with 1.8? |
@jeffkaufman Some of the custom paths didn't work in the |
@jeffkaufman So, even if I decide not use this feature as it's not been implemented in 1.8, which path should I use in the location - |
You're right, there's a big problem with I should be able to get a pull request out to fix this today, and we'll include it in the point release we're putting together. |
@jeffkaufman Thanks. |
This will be in 1.8.32.3 |
Backporting this to master for 1.8.31.3. Fixes #705.
@jeffkaufman Nice! Thank you! |
The documentation here https://developers.google.com/speed/pagespeed/module/configuration says that StaticAssetPrefix is now available and that the default path has changed to
/pagespeed_static
, but PageSpeed is giving an error thatStaticAssetPrefix
is not recognized and also the Nginx configuration still tells people to configure using/ngx_pagespeed_static
as location.The text was updated successfully, but these errors were encountered: