-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Apple's Broken Compression Handling] NSPOSIXError when trying to connect from Damus #3
Comments
This is strange. Try paste logs printed on the bostr2 server. |
Just checked, The error 100 is referring to failed HTTP/2 connections. It looks like it's trying to connect with HTTP/2, which is not supported by nhooyr.io/websocket lib yet |
You could try restart bostr2 with |
Majority of servers out here are using HTTP/1.1, and they worked most of the time. I checked the connection, Nothing wrong with header nor status. Just added an option to stop serving invalid Either way, You could test with the recent commit on master. Clone this repository, If still persist, and this problem is not able to be reproduced on bostr, Then my final guessing is the problem is on nhooyr's websocket lib. |
Looks like it has something to do with compression. |
Disabled compression due to it being unreliable at very certain cases. Could you try again with the recent commit? |
Added a code that disables compression on apple while keeping it on for others. Well well well. Right now, It should've fixed. But not a good fix unfortunately. |
Fixed on v1.0.1 |
I tried 1.0.1 and it worked as expected. |
Preparing before disaster happens. See Yonle/bostr2#3 Signed-off-by: Yonle <yonle@lecturify.net>
Hello.
When I try to connect to a bouncer from Damus app, it fails with
Error: Error Domain=NSPOSIXErrorDomain Code=100 "Protocol error" UserInfo={NSDescription=Protocol error}
and Damus attempts to reconnect over and over.Here is the screenshot:
My bostr2 instance is running with Go 1.21.12 on 14.1-RELEASE-p2, and is behind Caddy and Cloudflare.
The text was updated successfully, but these errors were encountered: