- From: Mark Shuttleworth <marks@thawte.com>
- Date: Mon, 10 Feb 1997 23:24:05 +0200 (SAT)
- To: Paul Foster <pfoster@ml.com>
- cc: ssl-talk@netscape.com, ietf-tls@w3.org
> Doesn't SSL/TLS over HTTP (aka HTTPS) set a precedent by using port 443
> instead of 80? Shouldn't this issue be resolved by now?
Yes it does, but it's not so bad.
1. HTTP *has* to be as lightweight as possible. If you used a trigger
like I just described you'd add another round trip at least.
2. The core part of the HTTP request comes on the first command from the
client to the server (the "GET" or "POST" or "PUT" etc.) so there's
not that much room to squeeze a trigger in.
For a critical, fast, lightweight protocol like HTTP even the purists
can probably make an exception ;-)
--
Mark Shuttleworth
Thawte Consulting
Received on Monday, 10 February 1997 16:23:20 UTC