You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! It looks like create-resource-handler and create-file-handler don't understand URL-escaped characters, so requests for files like foo%20bar.png will return a 404. Is it possible that I'm doing something wrong, or this is an intentional design choice? If not, would it be appropriate to URL-decode (:uri req) in the resource handler?
The text was updated successfully, but these errors were encountered:
I created a file public/foo bar.txt. Now http://localhost:3000/internal/foo%20bar.txt works as expected but http://localhost:3000/external/foo%20bar.txt returns 404. I'd say that they both should work and URL-decoding (:uri req) sounds about right.
Hi there! It looks like
create-resource-handler
andcreate-file-handler
don't understand URL-escaped characters, so requests for files likefoo%20bar.png
will return a 404. Is it possible that I'm doing something wrong, or this is an intentional design choice? If not, would it be appropriate to URL-decode(:uri req)
in the resource handler?The text was updated successfully, but these errors were encountered: