![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 10 years ago
Closed 10 years ago
#341 closed design (wontfix)
Multiple Spaces in status lines, request lines
| Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p1-messaging@… |
|---|---|---|---|
| Priority: | normal | Milestone: | unassigned |
| Component: | p1-messaging | Severity: | Active WG Document |
| Keywords: | Cc: |
Description
Some implementations ignore multiple spaces in status lines and request lines, e.g.,
GET / HTTP/1.1 200 OK HTTP/1.1
Currently, the ABNF only allows one space between the components.
SHOULD extra space here be BWS or OWS?
Change History (2)
comment:1 Changed 10 years ago by fielding@…
comment:2 Changed 10 years ago by mnot@…
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
There are no extra spaces allowed. That is the interoperable behavior. If some implementations choose to receive more than one space, that's their choice -- it is not interoperable to send more than one space. The ABNF defines what is valid to send.