Related issue/change:
#347
cc3e3cd
While using fabio a team mate noticed that some of our URL path parameters, such as resource Ids, which have url-encoded content in them are being decoded by fabio causing 404 errors. The decoded path parameters are sent to the service and not recognized as a valid path.
Example:
container/job with urlprefix-/posts
request: GET /posts/abcder%2Fsdf394/comments
This matches the URL prefix, but routes to /posts/abcder/sdf394/comments which isn't a valid path and thus returns a 404.
Related issue/change:
#347
cc3e3cd
While using fabio a team mate noticed that some of our URL path parameters, such as resource Ids, which have url-encoded content in them are being decoded by fabio causing 404 errors. The decoded path parameters are sent to the service and not recognized as a valid path.
Example:
container/job with
urlprefix-/postsrequest: GET /posts/abcder%2Fsdf394/comments
This matches the URL prefix, but routes to
/posts/abcder/sdf394/commentswhich isn't a valid path and thus returns a 404.