* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #218 (closed design: fixed)

Opened 4 years ago

Last modified 22 months ago

Explain non-HTTP URIs in HTTP

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: 20
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin:

Description

It's sometimes asked whether non-HTTP URI schemes can be used in a HTTP request.

While we don't need to completely specify this, p1 (and elsewhere?) should clarify whether it's possible, what implementations should do when they encounter a request scheme they don't understand, and common issues, e.g., what to do with the Host header.

Change History

comment:1 Changed 3 years ago by fielding@gbiv.com

From [1173]:

Clarify that gateways are just origin servers with additional proxy issues and then refer only to origin servers when describing their outbound requirements.

Consistently use the term URI instead of URL.

Rewrite the section on Host to be clear on where the information comes from and how proxies differ from other clients. Warn about security holes in stupid interception proxies.

Addresses #218

comment:2 Changed 2 years ago by mnot@pobox.com

Can this be closed as 'incorporated'?

comment:3 Changed 2 years ago by fielding@gbiv.com

From [1575]:

Explain first half of message routing. Related to #218.

comment:4 Changed 2 years ago by mnot@pobox.com

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

comment:5 Changed 2 years ago by mnot@pobox.com

  • Milestone changed from 19 to 20

Changing to -20 because it wasn't covered in the -19 summary.

comment:6 Changed 22 months ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:7 Changed 22 months ago by mnot@pobox.com

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