Martti T.
Martti T.
Consider this workaround - if you really need now to unescape path params that router creates you can escape them in middleware. ```go e.Use(func(next echo.HandlerFunc) echo.HandlerFunc { return func(c echo.Context)...
I am reluctant to accept this PR or any related to same issue with Router because the people that want to unescape params and have it as a problem have...
Is cause by https://github.com/labstack/echo/issues/1834
Maybe something like that would be better In case `X-Real-Ip` header is present we check if we can trust `Request.RemoteAddr` and If we can -we will use `X-Real-Ip` value. Also...
alright, done. I look this issue couple weeks ago but did not want to merge because I did not remember how this IP worked. Fortunately we have fairly good explanations...
NB: it is missing tests
unit tests are only for scheme parsing. this is only small part of that middleware. ---- Currently it introduces new header "forwarded" [RFC7239](https://datatracker.ietf.org/doc/html/rfc7239) which I think - if implemented should...
Are there logs of something panicking (sounds like that) or even an working example? Current description has not enough information.
closing not enough information
This is little bit too simple take for implementing this feature. I would say that the requirement we are talking is allowing multiple parameters per route segment where segment is...