Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1193

Mixing + and %20 in URL paths befuddles path parsing

    Details

    • Steps to Reproduce:
      Hide

      Clone the GitHub project here and follow the instructions.

      Show
      Clone the GitHub project here and follow the instructions.

      Description

      I've made a GitHub project here which makes it easy to reproduce this bug, it also includes a description.

      If I curl to a running Undertow at http://host:port/+/f%20oo it should parse the path parts as {{ ["+", "f oo"] }} but alas it doesn't. Instead, it replaces the {} with a space character. However, if I curl http://host:port/+/foo or curl http://localhost:8434/%2b/f%20oo I see the behaviour I expect, I get ["+", "foo"] and [ "", "f oo"].

      According to RFC 3986 section 3.3, a URL path can contain a +. Have you interpreted the RFC in a different manner than I?

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  swd847 Stuart Douglas
                  Reporter:
                  olasundell Ola Sundell
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: