Uploaded image for project: 'TorqueBox'
  1. TorqueBox
  2. TORQUE-955

Encoded backslashes in URL are not decoded correctly

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.1.2
    • Fix Version/s: 2.2.0
    • Component/s: Rack
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      1. Deploy a rack application like the following:

      run lambda { |env|
      [200,

      { 'Content-Type' => 'text/html' }

      , env.inspect]
      }

      2. Curl a URL with a encoded backslash
      curl http://localhost:<port>/foo%5Cfoo

      3. Examine the request.
      PATH_INFO and REQUEST_URI will be incorrect like the following
      "PATH_INFO"=>"/foo/foo"

      Show
      1. Deploy a rack application like the following: run lambda { |env| [200, { 'Content-Type' => 'text/html' } , env.inspect] } 2. Curl a URL with a encoded backslash curl http://localhost: <port>/foo%5Cfoo 3. Examine the request. PATH_INFO and REQUEST_URI will be incorrect like the following "PATH_INFO"=>"/foo/foo"

      Description

      A URL with an encoded backslash (%5C) will be sent to a rack application as a forward slash.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                benbrowning Ben Browning
                Reporter:
                jgilman Jason Gilman
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: