Bug 218560 - NSPOSIXErrorDomain:100 when loading content proxied from Apache by nginx
Summary: NSPOSIXErrorDomain:100 when loading content proxied from Apache by nginx
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: Safari 14
Hardware: Unspecified Unspecified
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-04 04:09 PST by Henri Sivonen
Modified: 2020-11-04 10:51 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henri Sivonen 2020-11-04 04:09:35 PST
Steps to reproduce:
1) Navigate to https://hsivonen.com/test/moz/

Actual results:
In Safari 14.0 (14610.1.28.1.10) on macOS Mojave 10.14.6, Safari says:

Safari can't open the page. The error is: "The operation couldn't be completed. Protocol error" (NSPOSIXErrorDomain:100)

In Safari on iPadOS 14.1, the error message is:

Safari could not open the page because the server stopped responding.

Firefox and Chrome load the page just fine. The page is proxied by nginx with Apache as the origin server. The same nginx instance also serves https://hsivonen.fi/ (served from flat files by nginx itself) and https://html5.validator.nu/ (proxied by with Jetty as the origin server), and Safari can load these pages from the same nginx instance.

Expected results:

Expected the page to load.
Comment 1 Henri Sivonen 2020-11-04 08:22:56 PST
This was resolved by adding
proxy_hide_header Upgrade;
to nginx config per
https://stackoverflow.com/questions/51266188/nsposixerrordomain100-error-on-safari-when-try-to-open-https

I'm leaving the bug open due to the error message being very uninformative.
Comment 2 Smoley 2020-11-04 10:51:27 PST
Thanks for filing. Safari error messages like these are handled outside of WebKit. Please file feedback at feedbackassistant.apple.com and reference this report. Thanks!