Details

    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 0.8.0
    • Fix Version/s: 0.9.0
    • Labels:
      None

      Description

      This is related to the issue in IMMUTANT-195. Looking through the code, I'm not sure if we can solve it. This issue can be tested with the escaper project on that issue:

      example:

      $ curl -v http://localhost:8080/foo%2Fbar

      • About to connect() to localhost port 8080 (#0)
      • Trying ::1... Connection refused
      • Trying 127.0.0.1... connected
        > GET /foo%2Fbar HTTP/1.1
        > User-Agent: curl/7.23.1 (x86_64-apple-darwin11.2.0) libcurl/7.23.1 OpenSSL/1.0.1c zlib/1.2.7 libidn/1.25
        > Host: localhost:8080
        > Accept: /
        >
        < HTTP/1.1 400 Bad Request
        < Server: Apache-Coyote/1.1
        < Content-Length: 0
        < Date: Fri, 22 Feb 2013 17:08:53 GMT
        < Connection: close
        <
      • Closing connection #0

      My expectation would be that a route /foo/:something/bar could match /foo/my%2Fvalue/bar with :something getting "my%2Fvalue" which could be url decoded as "my/value" by my app.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                norman Norman Richards
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: