URL encoded / breaks routing about atreugo

[savsgio]

Hi @Dadibom,

Could you give me more information or and example about the issue?

Because, Do you pass an encoded url into a url parameter like localhost/<my url>/parse or into a query param localhost/parse?url=<my url>??

[savsgio]

Sorry for delayed answer!

[bohyunjung]

@savsgio I'm quite sure that @Dadibom meant localhost/<my url>/parse as in your comment. When an encoded url which includes "%2F", encoded(or path-escaped) "/" is provided as <my url>, the router sees it as "/", not "%2F" as desired.

I'm also checking out various fasthttp-compatible routers if they support encoded path parameter, but haven't found one yet.