ISSUE-126: DNT-extension syntax includes characters not safe to embed in JSON
DNT-extension syntax includes characters not safe to embed in JSON
- State:
- CLOSED
- Product:
- Tracking Preference Expression (DNT)
- Raised by:
- Roy Fielding
- Opened on:
- 2012-02-15
- Description:
- The definition of DNT-extension in the FPWD includes a very wide set of characters because we had not made any decisions about extensions. However, if the field-value is going to be echoed back to the client, as in the current proposal for the tracking status resource, then we should reduce the characters allowed to a safe set that can be easily embedded in a JSON string.
- Related Actions Items:
- No related actions
- Related emails:
- Fwd: consensus and other process clarifications (from aleecia@aleecia.com on 2012-06-18)
- process clarifications (from aleecia@aleecia.com on 2012-04-05)
- Re: tracking-ISSUE-126: DNT-extension syntax includes characters not safe to embed in JSON [Tracking Preference Expression (DNT)] (from fielding@gbiv.com on 2012-02-20)
- Re: tracking-ISSUE-126: DNT-extension syntax includes characters not safe to embed in JSON [Tracking Preference Expression (DNT)] (from mts@zurich.ibm.com on 2012-02-20)
- tracking-ISSUE-126: DNT-extension syntax includes characters not safe to embed in JSON [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-02-15)
Related notes:
Fixed in r1.75
DNT-extension = %x21 / %x23-2B / %x2D-5B / %x5D-7E
; excludes CTL, SP, DQUOTE, comma, backlash
Display change log