Peter Liske

@proshin-roman: like @cowtowncoder mentioned in point (3) - just do not use the Creator method. My complete example for exactly your use case works really well up to date. Lombok...

Actually the bug is a combination of URI-unescaping together with normalization. Before #1547 already the unescaping was violating the W3C recommendations: According to https://www.w3.org/Addressing/URL/4_URI_Recommentations.html URL-sensitive characters > […] may NEVER...

The logging is not a problem

@aryszka Actually I would feel better not to decode the slash %2F. Then the URL normalization would also not hurt anymore.

Actually this very commit wanted to avoid what is happening right now: https://github.com/zalando/skipper/pull/1547/commits/d79a87f14bd1b9d98bb490932a85a248b40e42d1 Somehow the intention is not met.

@NorthFury but that also means that decoding %-characters should only happen if wanted, right?