Opened 12 years ago
Closed 12 years ago
#253 closed editorial (fixed)
clarify what LWS means for the Content-Disp grammar
Reported by: | julian.reschke@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | normal | Milestone: | unassigned |
Component: | content-disp | Severity: | Active WG Document |
Keywords: | Cc: |
Description
We do say that we use RFC 2616's ABNF syntax, but we should make it clearer what that means for the content-disposition syntax.
Change History (6)
comment:1 Changed 12 years ago by julian.reschke@…
- Summary changed from clarity what LWS means for the Content-Disp grammar to clarify what LWS means for the Content-Disp grammar
comment:2 Changed 12 years ago by julian.reschke@…
- Owner set to julian.reschke@…
comment:3 Changed 12 years ago by julian.reschke@…
comment:4 Changed 12 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from new to closed
comment:5 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:6 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
From [1060]:
Add more prose about implied LWS, also include quoted-string into the ABNF, and explain that value is "token | quoted-string" (see #253)