I'm not sure how specific this is to grizzly, so I hope I'm not way off
track by posting here.
I found that you can specify a "uriEncoding" property in the
http-listener, which was just what I was looking for. Unfortunately, it
didn't seem to fix the problem as I had anticipated.
From what I can tell, it doesn't seem to be encoding/decoding the URL
properly. When I pass a query (such as "Eugène") to the servlet, it
doesn't seem to receive it correctly encoded. The response, which (among
other things) simply dumps the GET parameters, is garbled. "EugeÌne" is
the text I get in the response.
Further, I am fairly confident that the garbling is happening before it
gets to the servlet, because (1) there are no matches, and there would
be if solr (the servlet) got the correct text and (2) the exact same
solr configuration is currently working properly under tomcat using
their Connector. Ideas?
Thanks any help you can offer.
Peter
Peter Cline wrote:
> Hi all,
>
> I posted this to the glassfish forums and it was suggested that I ask
> here. So, apologies to anyone who is reading this for the second time.
>
> I'm wondering if anyone knows how to configure glassfish to encode
> URLs in UTF-8. I'm considering moving to glassfish from tomcat as a
> servlet container (and more later). I'm running solr instances and
> need to be able to pass utf-8 encoded characters through the URL. With
> the default settings, it's using some other encoding and everything
> comes back garbled.
>
> In tomcat, I had to add a URIEncoding="UTF-8" attribute to the active
> Connector in the server.xml. I can't find any kind of an analog for
> this in glassfish, or any other place that seems obvious to specify
> this. Thoughts anyone?
>
>
> Thanks,
> Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>