Require decoding of plus as space in query part of URL

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.02
    • Affects Version/s: V4.01_OS
    • Component/s: Protocol
    • None
    • Hide

      Leave it as an option for servers to make moving to V4.02 as easy as possible.

      Make it a requirement for conforming clients, and add to section 13.3 Interoperable OData Clients between current rules 9 and 10:

      10. MUST encode the plus character (octet 0x2B) as %2B in URLs to avoid servers mis-interpreting the plus character as an encoded space

      Show
      Leave it as an option for servers to make moving to V4.02 as easy as possible. Make it a requirement for conforming clients, and add to section  13.3 Interoperable OData Clients between current rules 9 and 10: 10. MUST encode the plus character (octet 0x2B) as %2B in URLs to avoid servers mis-interpreting the plus character as an encoded space
    • Hide

      https://github.com/oasis-tcs/odata-abnf/pull/109
      https://github.com/oasis-tcs/odata-specs/pull/203

      Show
      https://github.com/oasis-tcs/odata-abnf/pull/109 https://github.com/oasis-tcs/odata-specs/pull/203

      The WhatWG URL specification defines an API for manipulating URLs that uses application/x-www-form-urlencoded for parsing and serializing query options.

      This API encodes space (octet 0x20) as "+" (octet 0x2B), and consequently decodes "+" (octet 0x2B) as space (octet 0x20).

       This is a follow-up to ODATA-1539.

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: