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 has been archived by the owner on Apr 21, 2023. It is now read-only.
What steps will reproduce the problem?
1. Configure your mod_pagespeed:
ModPagespeedDownstreamCachePurgeLocationPrefix http://localhost:80/
ModPagespeedDownstreamCachePurgeMethod PURGE
ModPagespeedDownstreamCacheRewrittenPercentageThreshold 95
2. Use a tool to look at incoming HTTP requests look for PURGE requests. If you
use varnish you can type:
varnishlog -m RxRequest:PURGE
3. Navigate to www.example.com/somepage.html
4. Look at your logs and look at the URL to which the PURGE request was sent
What is the expected output? What do you see instead?
I would like to see /somepage.html
What I see instead is I would like to see //somepage.html (note the double
slash)
What version of the product are you using (please check X-Mod-Pagespeed
header)?
1.6.29.7-3566
On what operating system?
Debian 7.0
Which version of Apache?
Apache/2.2.22
Original issue reported on code.google.com by hug...@betabrand.com on 2 Apr 2014 at 12:13
The text was updated successfully, but these errors were encountered:
Typo in the bug report:
"What I see instead is I would like to see //somepage.html (note the double
slash)"
should read:
"What I see instead is //somepage.html (note the double slash)"
Original comment by hug...@betabrand.com on 2 Apr 2014 at 12:15
As per the discussion in
https://groups.google.com/forum/#!topic/mod-pagespeed-discuss/qXDQ4FuQ-08
(parts of 4th, 5th and 6th mails on the thread), removing the trailing slash
from ModPagespeedDownstreamCachePurgeLocationPrefix fixes the double slash
issue noted here. What we should probably update the documentation to remove
the trailing slash in
https://developers.google.com/speed/pagespeed/module/downstream-caching#ps_downs
tream_conf
Assigning to Jan since he will most probably have more updates to this
documentation.
Original comment by anup...@google.com on 2 Apr 2014 at 1:44
Original issue reported on code.google.com by
hug...@betabrand.com
on 2 Apr 2014 at 12:13The text was updated successfully, but these errors were encountered: