<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 20, 2016 at 10:43 AM, Peter Schober <span dir="ltr"><<a href="mailto:peter.schober@univie.ac.at" target="_blank">peter.schober@univie.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">* Mark Juszczec <<a href="mailto:mark.juszczec@gmail.com">mark.juszczec@gmail.com</a>> [2016-10-20 16:21]:<br><span class="gmail-"><br>
> Yes. The common solution is to specify one or both of the following in<br>
> <Connector> in server.xml:<br>
><br>
> URIEncoding="UTF-8"<br>
> useBodyEncodingForURI="true"<br>
><br>
> Unfortunately that has no impact on my problem.<br>
<br>
</span>Those are for data that's part of the URL, no? As such those should<br>
have nothing to do with request.getAttribute() calls to data provided<br>
outside of query parameters?<br></blockquote><div><br></div><div>Based on my research I've found that these are the only ways to influence the encoding on parameters passed in the body of a GET.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Also, isolatin1 is only the "DEFAULT_CHARSET", i.e., when none is<br>
set. No idea when 'if (charset == null)' happens, but are you sure<br>
you've provided all means (HTTP, HTML) to the User Agent to make sure<br>
everything is UTF-8?<br>
<span class="gmail-"><br></span></blockquote><div><br></div><div>That's a good point. I've gone back and looked at the ByteChunk.getCharset()<br><br><div> public Charset getCharset() {</div><div> if (charset == null) {</div><div> charset = DEFAULT_CHARSET;</div><div> }</div><div> return charset;</div><div> }</div></div><div> </div><div>The data returned by HTTP is fine. Once it gets passed thru AJP, its not.<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
> I suspect its because my data, for whatever reason, is NOT coming to<br>
> me % encoded. mod_jk is putting it into environment variables and<br>
> the delivering it via AJP in the body of a GET.<br>
<br>
</span>Unrelated to your issue (which is one I think everyone shibbolizing<br>
Confluence ran into at some point), but last time I checked mod_jk<br>
didn't provide any features I absolutely needed to warrant the extra<br>
work of building it myself, when mod_proxy_ajp comes fully supported<br>
and often packaged by GNU/Linux distributions.<br>
It should have more features and tunables, though.<br></blockquote><div><br></div><div><br></div><div>Can you explain "shibbolizing Confluence" ?<br><br>I don't understand.<br> </div></div></div></div>