Opened 9 years ago

Closed 7 years ago

#218 closed design (fixed)

Explain non-HTTP URIs in HTTP

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

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 (7)

comment:1 Changed 8 years ago by fielding@…

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 8 years ago by mnot@…

Can this be closed as 'incorporated'?

comment:3 Changed 7 years ago by fielding@…

From [1575]:

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

comment:4 Changed 7 years ago by mnot@…

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

comment:5 Changed 7 years ago by mnot@…

  • Milestone changed from 19 to 20

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

comment:6 Changed 7 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:7 Changed 7 years ago by mnot@…

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