Re: draft-ietf-tls-http-upgrade reissued

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: kugler@us.ibm.com: "Re: Using Chunked encoding to send control messages to a client"
• Previous message: James Lacey: "Using Chunked encoding to send control messages to a client"
• Maybe in reply to: Scott Lawrence: "draft-ietf-tls-http-upgrade reissued"
• Next in thread: Julien Pierre: "Re: draft-ietf-tls-http-upgrade reissued"

Julien Pierre wrote:

> John Stracke wrote:
>
> > Just because a client always asks to upgrade doesn't mean the server has to obey.
>
> So how does that make the draft useful if the upgrade is never allowed ?

Who said never?

A client that wants to use the draft can ask for an upgrade on every HTTP request.
Servers that aren't willing to spend cycles on TLS for a particular request can just
ignore the Upgrade: header.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |"God does not play games with His loyal      |
|francis@ecal.com|servants." "Whoo-ee, where have you *been*?" |
|                |--_Good Omens_                               |
\==============================================================/

• Next message: kugler@us.ibm.com: "Re: Using Chunked encoding to send control messages to a client"
• Previous message: James Lacey: "Using Chunked encoding to send control messages to a client"
• Maybe in reply to: Scott Lawrence: "draft-ietf-tls-http-upgrade reissued"
• Next in thread: Julien Pierre: "Re: draft-ietf-tls-http-upgrade reissued"