Reduce extra RTT when setting up CONNECT tunnel in http outbound (not vmess through http) #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previous http outbound has 1 extra round-trip time to set up a CONNECT method tunnel. The client sends a CONNECT method request, waits for
200 OK
response from server, then sends tunnelled payload.This commit eliminates the extra RTT by sending first client payload (probably the ClientHello of tunnelled connection) immediately after the CONNECT method request, without waiting for
200 OK
from server. This mechanism has been implemented in NaiveProxy and proves to work.BTW, the Proxy-Connection header only takes effect for http/1.x, so I deleted it for h2.