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
ERR_METHOD_NOT_SUPPORTED, Opening handshake failed. #237
Comments
Not enough information about what you are doing here. What's your server, what's your client? |
Running the examples in this repository on Chromium. |
I'm not a Chromium maintainer. Either you help me pinpoint a problem specifically in the code I wrote or I suggest you look elsewhere for help. |
What happens when you run the WebTransport example code of Chronmium/Chrome? Do you get a handshake error? |
Following instructions at https://github.com/aiortc/aioquic/tree/main/examples on Chromium 99.0.4802.0 (Developer Build) (64-bit)
|
@guest271314 Have you got the way to fix this error? I am currently having this same problem. Thanks! |
@BruceChai-SM I have not found a fix. |
Same issue here, related comment I saw in the Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1011392#c107 |
@guest271314 I found a working code sample here: It's strange that WebTransport requires such a specific HTTP/3 server setup. |
@Niek Yes, that code runs, though does not support live-streaming. I also do not gather why Chromium authors who updated |
👍Yeah, I also found this example works today. |
Thanks, @guest271314 Can you share the link to the PR please? |
@BruceChai-SM Works in general, yes, using the code published, except for the unmerged PR that fixes reading bidirectional stream GoogleChrome/samples#752. I have not achieved the requirement of live-streaming media GoogleChrome/samples#756. The stream and datagram eventual grow in internal buffer size (should not be buffered at all), and stops streaming.
|
At terminal
At browser
Steps to reeproduce:
Follow instructions at examples/README for Chromium.
Potentially related GoogleChrome/samples#749 (comment), GoogleChrome/samples@b83dc66.
The text was updated successfully, but these errors were encountered: