After QUIC is enabled, the QUIC protocol is not implemented
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
- Only QUIC support is turned on. When using wireshark to analyze this cronet-sample, I did not see the packet content of the QUIC protocol. The 105 version of Cronet I compiled on Ubuntu also doesn't see the QUIC package contents. What is the reason? Tested with Samsung phone.
- Neither the demo nor Cronet(version 105) has QUIC enabled, and HTTP requests are still used. How to make the request only perform QUIC requests. It's very anxious. Thanks for the quick answer
- There is no CronetUrlRequestContext class in the Cronet library JAR package. Is this the cause of the above problem?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with the cronet-sample and Cronet version 105 on Ubuntu, observing traffic in Wireshark. Inspect the Cronet library JAR for CronetUrlRequestContext and compare the demo's request behavior. Done means the cause of HTTP fallback is identified and QUIC-only requests are verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100