Litespeed image optimisation won’t work with WP-Hide

Hi,
Can you try to set to No the “Block wp-cron.php” at WP Hide > Rewrite > Root Files ? The cron might be blocked internally if the server call it using a different ip than what domain use.

Thanks

Hi,

Thanks for your reply, the wp-cron isn’t blocked in the rewrite root files section?

Hi,
I’ll try to replicate the issue on this side, can you send more details upon the cache application you use, also how to replicate the reported issue.

Or please feel free to contact us directly.

Thanks

Hi, thanks for your reply, missed the notification.

Replication should be simple, install wp-hide and try the cron based image optimisation. It fails. I checked access to the media folders inside of wp-hide, they’re not blocked.

The cache is Litespeeds own cache plugin.

https://en-gb.www.ads-software.com/plugins/litespeed-cache/

It’s so frustrating to have to disable wp-hide each time to manually send the optimisation request, then wait, then pull the optimised images back. Normally, with cron enabled it should just do this automatically, but for some reason, something inside of wp-hide is blocking the communication between litespeed and their servers? Or maybe it’s a path issue ?

From their response when I showed sample .htaccess from wp-hide…

from that htaccess content

RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in.*$ [NC]
RewriteRule ^wp-content(.+) /index.php?wph-throw-404 [L]
so if I am interpreting it correctly :

If the incoming request doesn’t have REDIRECT_STATUS status , and doesn’t have wordpress_logged_in cookie , then every request to wp-content, like image URL /wp-content/uploads/2020/02/some.jpg will redirect to index.php?wph-throw-404

Am not sure how to solve this, have asked them if they have a solution, but is this the problem?

They found the problem, they said that their requests were being redirected to a 404, so suggested the following workaround. I tested it and it does work. Something to think about for new versions maybe?

Yeah , it seems redirect it to 404 page as I assumed.

A quick workaround , try make that block to be

RewriteCond %{HTTP_USER_AGENT} !LiteSpeed-Image
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in.*$ [NC]
RewriteRule ^wp-content(.+) /index.php?wph-throw-404 [L]
this will add a condition check

RewriteCond %{HTTP_USER_AGENT} !LiteSpeed-Image

that if user agent is LiteSpeed-Image, which is our image server uses , will bypass that 404 redirect rule.

Hi,
Thanks for your additional feedback, it does make sense. I’am not sure why they are still calling the images through the old urls, but I’ll check it further. Or the rewrite update you provided, will be fine too.

Thanks

Something removed the entry from the .htaccess and it failed again, is there anywhere inside of wp-hide that I can make sure this entry stays in place?

I think (not that I know much) that the reason they’re calling the old URLs is because their entries in .htaccess come before the ones for wp-hide? Would that be a reason?

It would be really good to have wp-hide compatible with all litespeed servers out there that are using image optimisation.

Hi,
If the permalinks updated/re-generate, the wp-hide outputs the default rewrite. Until we include a fix for this issue, you can change the permission of .htaccess file so it won’t be changed from php.

Thanks

Great idea about permissions, thanks.

Just saying thanks for adding this now to new versions going forward.

• This reply was modified 4 years, 8 months ago by Audiomonk.