![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
#378 closed editorial (incorporated)
is "q=" case-sensitive?
| Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p1-messaging@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 21 |
| Component: | p1-messaging | Severity: | Active WG Document |
| Keywords: | Cc: |
Description
Per ABNF, it is not. Is this true in practice (if yes, maybe clarify in prose).
Change History (8)
comment:1 Changed 6 years ago by julian.reschke@…
- Summary changed from is "q=" case-sensitive to is "q=" case-sensitive?
comment:2 follow-up: ↓ 3 Changed 6 years ago by fielding@…
comment:3 in reply to: ↑ 2 Changed 6 years ago by julian.reschke@…
Replying to fielding@…:
I noticed the same thing while editing last night and actually changed it to %x71,
That's why I noticed.
but changed it back before committing to avoid making any technical changes.
+1
Apache httpd's implementation is case-sensitive.
We probably should check at least another one (Tomcat), and in case it has the same restriction, restrict it to lowercase.
comment:4 Changed 6 years ago by fielding@…
Er, no, my mistake ... Apache httpd does a tolower before comparison, so it is case-insensitive. CERN httpd is case-insensitive. Nginx only implements q for accept-encoding, but for that it is case-insensitive.
comment:5 Changed 6 years ago by julian.reschke@…
Ok. So maybe just add prose pointing out that it's case-insensitive?
comment:6 Changed 6 years ago by fielding@…
comment:7 Changed 6 years ago by fielding@…
- Milestone changed from unassigned to 21
- Resolution set to incorporated
- Status changed from new to closed
I noticed the same thing while editing last night and actually changed it to %x71, but changed it back before committing to avoid making any technical changes.
Apache httpd's implementation is case-sensitive.