-
Notifications
You must be signed in to change notification settings - Fork 712
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
Opening a pipe fails on first attempt #1095
Comments
@tomwilkie said it's by design, but should be 404 instead of 400... |
It is by design :).
So we might be able to "fix" this in the client by checking if a pipe exists w/ a WS connection instead, I forget if we tried to do that in the past and it didn't work for some reason... Or the server could add a new endpoint that is not a WS that returns a 200 if a pipe exists. |
I will try in the client first. |
Oh yeah you can't read the http response code from a WS for browser security reasons. Earlier discussions #650 (comment) We'd need a new server endpoint. |
Dupe of #994 |
The text was updated successfully, but these errors were encountered: