Closed (duplicate)
Project:
Purge
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Aug 2012 at 13:43 UTC
Updated:
28 Aug 2012 at 13:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
heddntesting still needed on a more production like environment than just my local workstation. that comes next...
Comment #2
SqyD commentedThank you for your bug report. Not sure if I understand you correctly since I don't know the redirect module. Could you help me clarify?
- Varnish can and will cache redirects, so purging/banning them might be useful in other cases.
- Your patch seems a rather blunt workaround that may (or may not) have unintended side effects.
- Wouldn't it be a more elegant solution to make expire aware of the redirect module and have an option to exclude those url's from the expire logic before they are handed over to purge?
Like your said this case would require more testing which I unfortunately don't have too much time for lately but I would like to help you out if you could gather some more info and test results.
Comment #3
heddnI'm doing more research today with a fresh set of eyes. I'm not so sure that the patch is needed... I'm thinking it is an issue with how expire.module is sending down the hostnames. It seems to be tacking together the path and the hostname. So, instead of http://www.example.com/location, it is a url of http://www.example.comlocation.
Comment #4
heddnsee expire.module: #1471926: Invalid expire URLs when "Include base URL in expires" is enabled.