![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 9 years ago
Closed 9 years ago
#460 closed design (fixed)
Via and gateways
| Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p1-messaging@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 23 |
| Component: | p1-messaging | Severity: | In WG Last Call |
| Keywords: | Cc: |
Description (last modified by mnot@…)
p1 Section 2.3 says:
However, an HTTP-to-HTTP gateway that wishes to interoperate with third-party HTTP servers must conform to HTTP user agent requirements on the gateway's inbound connection and must implement the Connection (Section 6.1) and Via (Section 5.7.1) header fields for both connections.
This means that accelerators and CDNs MUST generate a Via header on the outbound connection. This isn't widely practiced, and I'm not sure it's necessary. Comments?
Change History (7)
comment:1 Changed 9 years ago by mnot@…
- Description modified (diff)
comment:2 Changed 9 years ago by mnot@…
- Milestone changed from unassigned to 23
comment:3 Changed 9 years ago by fielding@…
comment:4 Changed 9 years ago by fielding@…
- Resolution set to incorporated
- Status changed from new to closed
comment:5 Changed 9 years ago by julian.reschke@…
comment:6 Changed 9 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:7 Changed 9 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
Relax the MUST generate Via on responses from gateways, provided that they don't removing any existing Via header.