Describe the bug
We see some cases when optimization is not working where Imagify Tools shows that the optimization self-requests seem to be redirected infinitely between the HTTP and HTTPS versions. Here is an example Tools output when things are working correctly:
And here is an example of the Tools output when the issue is happening:
But it can also happen when there are cURL error 28's too:
In the end, the solution involved disabling Cloudflare (changing to development mode did not help) and flushing DNS cache.
Expected behavior
I'm not completely sure if the fault of this lies with Imagify or in the users' website/server settings (Cloudflare, SSL, etc). So I'm not sure if it's a case where Imagify should be flexible enough to work in these instances or if there are some instances where optimization can't or shouldn't work.
If it's the former, then it would be good to have an update to prevent these errors from happening.
If it's the latter, it could be good to have an investigation into the causes of this so we could at least make better suggestions to users facing this issue.
It may also be good to have a specific error message/popup for when this is happening so we can link to either Optimization is Stuck (with a specific section on this added) or to a doc page dedicated to this issue.
Describe the bug We see some cases when optimization is not working where Imagify Tools shows that the optimization self-requests seem to be redirected infinitely between the HTTP and HTTPS versions. Here is an example Tools output when things are working correctly:
And here is an example of the Tools output when the issue is happening:
But it can also happen when there are cURL error 28's too:
To Reproduce Not sure how to reproduce this at the moment, though there was a case some time ago where the issue may have been related to Cloudflare. Here are the conversations I had about that for more context: https://secure.helpscout.net/conversation/1248276713/185279 https://secure.helpscout.net/conversation/1355848899/219518 https://secure.helpscout.net/conversation/1387343008/228846/
In the end, the solution involved disabling Cloudflare (changing to development mode did not help) and flushing DNS cache.
Expected behavior I'm not completely sure if the fault of this lies with Imagify or in the users' website/server settings (Cloudflare, SSL, etc). So I'm not sure if it's a case where Imagify should be flexible enough to work in these instances or if there are some instances where optimization can't or shouldn't work.
If it's the former, then it would be good to have an update to prevent these errors from happening.
If it's the latter, it could be good to have an investigation into the causes of this so we could at least make better suggestions to users facing this issue.
It may also be good to have a specific error message/popup for when this is happening so we can link to either Optimization is Stuck (with a specific section on this added) or to a doc page dedicated to this issue.
Backlog Grooming (for WP Media dev team use only)