Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I'm using the CAS module which redirects to our centralized CAS login.
Because of this, when advagg scans the 'cas' path I get:
HTTP requests to advagg for css files are not getting through.
HTTP requests to advagg for js files are not getting through.
Is there a way to tell advagg to ignore this path so I don't have the errors show up?
Also, if I do have these errors, do they affect the functioning of advagg?
Comment | File | Size | Author |
---|---|---|---|
#7 | advagg-2164243-7-add-CAS-module-to-readme.patch | 1.17 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedLooks like there is a setting
cas_exclude
you can adjust to make the CAS module work with AdvAgg. If you go toadmin/config/people/cas
and under Redirection there should be a setting called "Excluded Pages". Add the following to the listComment #2
ghosts CreditAttribution: ghosts commentedThanks for the fast reply. I tried your suggestion and then cleared the AdvAgg cache (and then when that didn't work all caches). The error isn't CAS not working with AdvAgg rather, AdvAgg not playing nice with CAS.
Here is the error from the status report (I have a similar one for css files):
It seems the problem is that AdvAgg can't get a 404 because it hits a redirect.
Here is the raw output (edited for privacy):
If someone who knows this module better than me was to give me a hint of where to find in the code where AdvAgg look for files to aggregate I can look for a solution. The module is functioning well--I just would like to remove the status report errors which sometimes freak out my administrator users.
Comment #3
mikeytown2 CreditAttribution: mikeytown2 commentedAdvAgg has hidden settings. If you wish to disable the 404 check, add this to your settings.php file.
My understanding from the initial support request was that the CAS module was creating the redirect. Do you know what is causing the 302 redirect?
Comment #4
ghosts CreditAttribution: ghosts commentedThe CAS module creates the redirect. We are a university and require all users to authenticate through our central CAS server. A login maps to the path ./cas which is the source of the 302 to our centralized CAS server.
#3 removed the status report errors.
Thank-you.
Comment #5
mikeytown2 CreditAttribution: mikeytown2 commentedFollowing the advice from #1, you could try this as the double wildcard match might not have worked.
Going to mark this as fixed (as you seem happy) but allowing advagg to generate files on demand would be a good idea.
Comment #6
ghosts CreditAttribution: ghosts commentedI am quite impressed by your quick replies.
I undid #3 (disabling 404 checking in settings.php) and then followed your advice on #5 and no status report errors.
I am happy now. Thank-you!
Comment #7
mikeytown2 CreditAttribution: mikeytown2 commentedAfter looking at the CAS code you should add in services/* as this is excluded by default
http://drupalcode.org/project/cas.git/blob/d1d8bde786469c643ce2e94f36df8...
The following code has been committed.
Note that the patch is missing services/* but the actual commit has it in
http://drupalcode.org/project/advagg.git/commitdiff/c4677990400421ce05f7...