<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 21, 2015 at 8:04 PM, Matt Wringe <span dir="ltr"><<a href="mailto:mwringe@redhat.com" target="_blank">mwringe@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
This is not just an issue with the Kubernetes proxy, its also an issue<br>
with EAP, other web server, other apache components (or at least some<br>
older versions), and apparently a bunch of other proxies servers out<br>
there. Its a common enough problem in this space that we have already<br>
ran into in two places when dealing with OpenShift integration work.<br>
<br>
I don't think its acceptable to say that since we are compliant, its not<br>
our fault and we wont to anything to help get anyone get around this<br>
issue. We need to work in the real world and this means having to<br>
(potentially) deal with the common problems which exist out there.<br></blockquote><div><br></div><div>+1</div><div>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?)</div><div><br></div><div>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).</div><div><br></div><div><br></div></div></div></div>