You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
In the past 3 months I have not been able to access the Weather Network page on Safari. I receive this error statement: NSPOSIXErrorDomain:100.
Can anyone advise a solution to this issue?
iMac (27-inch, Late 2012), OS X Yosemite (10.10)
Problem is HTTP/2
When requesting the site using curl (command line) You'll get this response:
curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
When HTTP/2 is disabled, it works again.
Problem is HTTP/2
When requesting the site using curl (command line) You'll get this response:
curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
When HTTP/2 is disabled, it works again.
So we looked at this issue a little further.
When doing a "curl -iv domain.com"
You'll see that you receive a double header.
When using nginx in front of apache, only enable http2 in nginx.
If it's enabled also on apache, you get this error.
This error does only occur on Safari 11 and IOS 11.
I've seen this a few times but have yet to find a fix. Lot's of people wonder if its plugin issues, SSL issues or configuration problems but none have solved it.
They resorted to downloading Chrome.
I found a solution in the suggested Mac fixes. I was only having problems viewing content from one site (Weather Network). The solution was to go into Safari Preferences, under Privacy and list all Details. This provided a log of all sites where cookies, etc had been used. I found the Weather Network domain page and cleared all content from it. I was then able to reload the Weather Network page with no issues. I assume this would work for other similar singular sites.
Could you translate this to normal Language? I’m not able to understand it as it is right now.
@Robinbr1703 It's intended for developers as it is for them to fix the issue for their websites.
NSPOSIXErrorDomain:100
