[OASIS Issue Tracker] Commented: (ODATA-127) Whitespace in URLs must be percent-encoded

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31517#action_31517 ] 

Ralf Handl commented on ODATA-127:
----------------------------------

Instead of removing *WSP from places where it isn't required (e.g. after parentheses or commas) we could follow the example of the httpbis working group and use "bad whitespace" in places where it is undesired, yet not strictly forbidden, see http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-21#section-3.2.1:

   BWS is used where the grammar allows optional whitespace, for
   historical reasons, but senders SHOULD NOT produce it in messages;
   recipients MUST accept such bad optional whitespace and remove it
   before interpreting the field value or forwarding the message
   downstream.

     OWS            = *( SP / HTAB )
                    ; "optional" whitespace
     RWS            = 1*( SP / HTAB )
                    ; "required" whitespace
     BWS            = OWS
                    ; "bad" whitespace


> Whitespace in URLs must be percent-encoded
> ------------------------------------------
>
>                 Key: ODATA-127
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-127
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ABNF Construction Rules v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>            Priority: Minor
>             Fix For: WD01
>
>
> Some ABNF construction rules for URL constituents allow whitespace, e.g. rules contributing to the $filter system query option. Currently these rules use the WSP sub-rule which allows the space and horizontal-tab character. These characters are not allowed in URLs and must be percent-encoded.
> So we need to either
> - redefine the whitespace rule to 
>      WSP = "%20" / "%09"
> or
> - define a rule for precent-encoded whitespace 
>     peWS = "%20" / "%09"
>   and use it in URL-relevant rules.
> The latter approach is more explicit and less misleading as the current definition of WSP is a widely used convention

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira