-
-
Notifications
You must be signed in to change notification settings - Fork 47
Page Cache Compatibility Mode #39
Comments
@amiga-500, maybe the problem was introduced with this commit 954b739 (#24) I think that the problem is:
is not safe on Apache < 2.4 with module I found some info on stackoverflow. Step to reproduce
Possible fix
but this require @joshin42, thanks for your testing! |
I think @nigrosimone is right. Here's what I would suggest we use for the "If" blocks
We could probably just shrink it down to
But the first block is there for minimizing any false positives |
Agreed with the diagnosis, thanks! :) Yes, we're still on 2.2, Sites with compatibility mode are (even our) edge cases & we can disable it on them without problem Thankfully, we'll finally be moving to 2.4 in a month or two. |
@joshin42 i have applied @charlesLF suggestion. Can you test the master? |
Thanks @nigrosimone, it seems to be working fine now! -J |
@joshin42 Thanks! |
sorry my mistake. and the belated reply. And thx for the fix . I noticed when i had written e4efc3f i apparently didnt notice mod_authz_host was also available in 2.2...yikes! When i researched this at the time it seems i was looking incorrectly under 2.0 modules (mod_authz_host doesnt exist for it) mistakenly thinking i was researching all things pre-2.4. whoops! thx again |
No problem Kimberly! ; ) |
Howdy,
When upgrading sites that from 0.9.4.1 to today's pull, I encountered an error when compatibility mode was enabled. Our environment works fine with it off, so I have a work around.
I can replicate this on multiple sites and servers. The error looks like this:
[Tue Aug 30 18:15:28 2016] [crit] [client 24.56.43.116] configuration error: couldn't perform authentication. AuthType not set!: /wp-content/cache/page_enhanced/www.clientsite.com//category/faith//_index.html_gzip, referer: http://www.clientsite.com/
The pair of //'s in the path seem to be the culprit.
Sorry that I suck at coding or I'd be more useful and contribute fixes. I'm happy to test the latest code on some busy sites I manage & write up interesting things I find.
-J
The text was updated successfully, but these errors were encountered: