[OASIS Issue Tracker] Created: (ODATA-46) Inconsistent use of leading and trailing slashes in URI path parts

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

Inconsistent use of leading and trailing slashes in URI path parts
------------------------------------------------------------------

                 Key: ODATA-46
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-46
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData ABNF Construction Rules v1.0
    Affects Versions: WD01
         Environment: [Proposal]
            Reporter: Ralf Handl
             Fix For: WD01


Most, but not all, rules for URI path parts define a leading slash and no trailing slash.

Unfortunately some of these rules are used in places where no leading slash is allowed (property names in $filter, $orderby), see ODATA-28 and ODATA-29.

Also a few other rules or rule parts define neither leading nor trailing slashes, leading to missing path separators, or explicitly introduce a trailing slash, leading to two consecutive slashes.

At the root of this issues lies the question: does the serviceRoot have a trailing slash?

The spec explicitly says "No", while most server implementations explicitly say "Yes", and redirect from the slash-less path to the path with trailing slash before responding with 200 OK.

-- 
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