Uploaded image for project: 'Gateway'
  1. Gateway
  2. GTWY-2713

Design for Proper Encoding for all URLs and URIs in our Database

XMLWordPrintable

    • Icon: Defect Defect
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • Recycle Bin
    • 1.3.2
    • Database
    • None

      Currently our User's can have openids that might require url/uri encoding.

      Fictitious Example:
      https://www.earthsystemgrid.org/myopenid/nathan hook

      When properly encoded the above url will look like the following:
      https://www.earthsystemgrid.org/myopenid/nathan%20hook

      Unfortunately, URL/URI encoding is a one direction encoding. Once a URL/URI is encoded it is difficult programatically to determine if a URL/URI is properly decoded.

      For example, if I chose the following for my openid (looks suspiciously like the encoded url above):
      https://www.earthsystemgrid.org/myopenid/nathan%20hook

      The encoding for the new url would be the following:
      https://www.earthsystemgrid.org/myopenid/nathan%2520hook

              Unassigned Unassigned
              nhook Nathan Hook
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: