Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NSPOSIXErrorDomain:100 on Safari only 14.8 and above. #35119

Closed
ghost opened this issue Sep 9, 2020 · 7 comments
Closed

NSPOSIXErrorDomain:100 on Safari only 14.8 and above. #35119

ghost opened this issue Sep 9, 2020 · 7 comments

Comments

@ghost
Copy link

ghost commented Sep 9, 2020

  • Version: 14.8 and above (14.8, 14.9, and 14.10)
  • Platform: Windows

What steps will reproduce the bug?

A simple GET request using express framework is working fine on all browsers but failing on Safari for iOS and Mac with an error NSPOSIXErrorDomain:100. Degrading NodeJS to 14.7 is resolving the issue immediately. Any tips?

@bnoordhuis
Copy link
Member

Can you post steps to reproduce using only built-in modules (i.e., no express)?

FWIW, NSPOSIXErrorDomain:100 is EPROTO, meaning Safari complains about protocol trouble. It's possible it doesn't like the Keep-Alive: timeout=<seconds> header Node.js started sending in v14.8.0 (commit 36fd3da) but it seems unlikely.

@bnoordhuis
Copy link
Member

FWIW, it's possible that aforementioned commit contains a bug that #35138 addresses.

@bnoordhuis
Copy link
Member

Closing, no follow-up.

@ghost
Copy link
Author

ghost commented Sep 18, 2020

I just installed NodeJS v14.11 on our server and I still get the same error. Degrading to v14.7 is resolving the issue immediately.

@bnoordhuis
Copy link
Member

@fadijabi #35138 hasn't been released yet but you can build from source to try it out, it's on the v14.x-staging branch.

If #35138 doesn't fix it, then please post steps so I can reproduce locally.

@ghost
Copy link
Author

ghost commented Sep 23, 2020

This is to confirm that #35138 fixed the issue.

@bnoordhuis
Copy link
Member

Good to hear, thanks for following up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant