Needs review
Project:
Cache Expiration
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jun 2018 at 11:48 UTC
Updated:
22 Jun 2018 at 09:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
scott_euser commentedProposed patch attached.
Comment #3
scott_euser commentedComment #4
fgjohnson@lojoh.ca commentedHi Scott,
We use Varnish, Expire and memcache and have a similar issue perhaps.
Is this what you were trying to fix?
Basically when we select (recommended) the "Include base URL"; appropriate relative links get generated to expire (we can see in watchdog)... but nothing is actually expiring.
BUT if we enable "Include base URL" (not recommended) the full URL to the nid, and pathauto URL, of updated node is sent and expires correctly.
However - We are a multilingual site and we use custom URL's also for generated pages.... and the "Full path" generated in the "enabled" case includes the extra /en which is my home page.
I will try your patch and see what the effects are.
Comment #5
fgjohnson@lojoh.ca commentedFTY - The patch should reside in the root of the expire module not in docroot.
Comment #6
scott_euser commentedAh apologies for that - was an old project using mercurial so the diff went from the root instead of project; sorted attached.
In our case it is similar but, the homepage of the website is like https://www.example.com/en (ie, ) and a stylesheet we are trying to expire on gulp compile is like https://www.example.com/sites/all/themes/our-theme/assets/css/style.min.css. Without the patch, the module automatically attempts to expire https://www.example.com/en/sites/all/themes/our-theme/assets/css/style.m... instead. Same problem with custom hook_menu() routes used for various callbacks + rest API routes.
Relying on $base_url set by core instead should be a more accurate reflection of the domain.