Wp-rocket: err_failed and NSPOSIXErrorDomain:100 errors on certain Apple / iOS browsers

Created on 26 Oct 2018 · 10Comments · Source: wp-media/wp-rocket

On certain version of iOS and Safari some users (two so far) get err_failed and NSPOSIXErrorDomain:100 errors. Opening this issue so that we can track this and see if we can find the cause.

Known browsers with issues:

Safari Browser 11.0.2 on OSX High Sierra
Chrome for iOS - Version 69.0.3497.105
Safari - Version 12.0 (14606.1.36.1.9)

To reproduce this:

Load the website on a browser with issue.
Go to a second page.
Visit the homepage back by clicking on the logo or link to homepage.
Do this a few times if needed.
A very detailed note is added here.

Solutions that worked:

Comment out this and this in process.php.
For the second case, I had to comment out this and this as well.
For a desktop browser this worked once - https://discussions.apple.com/thread/7612610
Upgrade to the latest browser versions. (No issues on Chrome for iOS - Version 70.0.3538.75, Safari iOS 12.0.1, Chrome for iOS - Version 70.0.3538.77)

Theories and guesses:

WP Rocket sends a 304 response and this turned out to be the cause in one case.
Somehow iOS sends the wrong header and WP Rocket sends back the head without the body (as expected in a 304 response) and the browser has nothing to show.
All I could find related to this was this: http://andrewmarinov.com/ioss-corenetwork-lying/
This line: That being the case, though, iOS doesn’t automatically send out the If-Modified-Since header on the way back.
I am not even sure if it applies to this case. Because if there is no If-Modified-Since header, this line would simply fail and there would be no 304 response.

Tickets:

HS tag: err_failed

htaccess testing bug

Source

arunbasillal

Most helpful comment

Comment out these 2 parts works:

Ref ticket: https://secure.helpscout.net/conversation/836744613/105585?folderId=1213662

WordPresseur on 29 Apr 2019

👍3

All 10 comments

Can confirm that fixing #762 did not resolve this. Apple and their weirdness.

arunbasillal on 16 Nov 2018

@Tabrisrp I am not why this is happening, but consistently the solution was to stop the 304 response that WP Rocket sends.

I know this is not a perfect situation. Is it feasible to think of a filter with which we can turn off the headers and the 304 response that we send? These ones:

https://github.com/wp-media/wp-rocket/blob/82680e5c8884c4c08bf547f4d4802d4b7d8cb93f/inc/front/process.php#L484-L507

https://github.com/wp-media/wp-rocket/blob/82680e5c8884c4c08bf547f4d4802d4b7d8cb93f/inc/front/process.php#L521-L544

arunbasillal on 27 Nov 2018

Another case: https://secure.helpscout.net/conversation/724140697/89210?folderId=377611

In case it's revealing in any way, the customer also referenced this thread where at the end a solution is proposed from the server side:
http://forum.directadmin.com/showthread.php?t=55803

webtrainingwheels on 5 Dec 2018

Had one more of this happen - https://secure.helpscout.net/conversation/730059226/90062/
Tested to make sure that the fix we added for #762 wasn't the cause.

Note to self: Re-evaluate our 304 process and see if we are doing something wrong.

arunbasillal on 21 Dec 2018

Also having this issue, first I tried this
http://forum.directadmin.com/showthread.php?t=55803 although I'm not using nginx so I added
Header unset Upgrade
to my http2 config

That didn't fix it, this however did