Re: [Exist-open] Encoding issue using TOMCAT or a browser

[fkalich <fk...@at...>]

> But if I put this code into a servlet, what is sent back to a client, and
> also the Tomcat server prints to the console looks like this.....

I would understand if only some characters in your output were 
unreadable, but it looks completely messed up.

Does your servlet return a proper Content-Type header, e.g. "text/xml; 
charset=utf-8"? You also need to make sure that the response stream uses 
utf-8, e.g. by wrapping it into an OutputStreamWriter(ouputStream, "UTF-8").

Wolfgang

------------------------------------------------------------------------------

Sorry Wolfgang for the direct reply, I did not realize that would go to your
email, I am new here.  I will put my reply here


Thanks for your reply. The response had been set as you instruct.  I also
tried wrapping it as you said.  No change.  Have tried the server on a
Windows box, and Linux.  But this is weird.   The address to get it right
out of the eXist webapp on Tomcat is
http://192.168.1.67:8080/exist/rest//db/admin/default/SeInvSearch/IDLE/TheRule. 
I am not sure where I got that from, but I am sure that is what it is.  If I
put that in my browser, it asks for the application to view it in, and says
it is application/octet data.  If I choose WordPad it all looks real nice. 
If I use Notepad it is not quite right, but the only bad characters are some
zeros, and it is missing some things.  If I give the actual servlet address
http://192.168.1.67:8080/AutoOp/servlet/ActionStatusRule?action=fetch&roleName=admin&configName=default&clusterName=SeInvSearch
I get all the mass of junk.  Weird thing is that Wordpad reads it fine.  I
am real confused by all this.

-- 
View this message in context: http://www.nabble.com/Encoding-issue-using-TOMCAT-or-a-browser-tp22020144p22021505.html
Sent from the exist-open mailing list archive at Nabble.com.