On Mon, Sep 21, 2015 at 8:04 PM, Matt Wringe <mwringe@redhat.com> wrote:

This is not just an issue with the Kubernetes proxy, its also an issue
with EAP, other web server, other apache components (or at least some
older versions), and apparently a bunch of other proxies servers out
there. Its a common enough problem in this space that we have already
ran into in two places when dealing with OpenShift integration work.

I don't think its acceptable to say that since we are compliant, its not
our fault and we wont to anything to help get anyone get around this
issue. We need to work in the real world and this means having to
(potentially) deal with the common problems which exist out there.

And it's not the first time I hear about this issue, didn't we have that issue in RHQ ? (and change EAP default parameters?)

I would vote on forbidding / in URLs (metricsId...) if that's the issue (and likely be even more conservative)... URL encoding/decoding is a mess we cannot fix for others (proxies).