FAQ: explain the case where URL path contains escaped slash `%2F`

For example, i’ve set up the following route with field expression:

/user/{name}

However sometimes the variable will contains slashes /, such as:

/user/foo/bar

I know the slash character is a reserved character of URL, so i encoded my request URL as below:

/user/foo%2Fbar

I was expecting receiving the argument name with value foo/bar in responder method, but instead, i got a 404 error.

[vytas7]

Yes, but note that Werkzeug added this behaviour to their dev server, but not to parsing of the request path.

Their updated docs state:

If you want to route based on this value, you can use middleware to replace PATH_INFO in the environ before it reaches the application. However, keep in mind that these keys are non-standard and not guaranteed to be present.

Which what this issue is about, just for Falcon – documenting this, and adding recipes not dissimilar to what I’ve provided in my comments above 😈

[flying-sheep]

Great! I think first class support will still be nice but the recipe is a good step for people who need this now.