简体   繁体   中英

Start processing before SSL/TLS negotiation completes?

So looking at network time information for HTTPS page being loaded, one can see that (in my case) SSL/TLS negotiation takes ~50ms (a significant part of whole page). My understanding is that that server should now url before negotiation completes, and one could assume that negotiation mostly always succeeds. So it would seem that web server could start processing request before negotiation completes?

Does anyone know if that can be done (like web server option, start processing before negotiation completes)? Maybe it is already being done? Some reasons why it is not possible? Or why this is stupid idea?

The server does not know the URL before TLS negotiation completes. The requested URL is the first of the HTTP headers, which are wrapped and encrypted inside the TLS tunnel. Before the TLS tunnel is established the client cannot send and the server can't receive the HTTP headers.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM