Opened 10 years ago

Closed 10 years ago

#383 closed design (fixed)

Semantics of HTTPS

Reported by: mnot@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 21
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:


<> is slated to define the semantics of HTTPS urls.

We currently talk about HTTPS' impact on caches and identity there, but we don't mention one other major effect on HTTP -- the use of CONNECT to proxies.

I think we need to define HTTPS as having a semantic of *end-to-end* use of SSL/TLS, and therefore CONNECT to proxies.

Change History (5)

comment:1 Changed 10 years ago by fielding@…

From [1903]:

https requires and end-to-end secured connection. Addresses #383

Refer just to TLS, not SSL/TLS.

comment:2 Changed 10 years ago by fielding@…

  • Milestone changed from unassigned to 21
  • Resolution set to incorporated
  • Status changed from new to closed

comment:3 Changed 10 years ago by julian.reschke@…

From [1904]:

Record changes for [1903], see #383

comment:4 Changed 10 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:5 Changed 10 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.