Not logged in : Login
(Sponging disallowed)

About: FAQ/CharacterEncoding - Tomcat Wiki     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : owl:Thing, within Data Space : www.openlinksw.com associated with source document(s)
QRcode icon
http://www.openlinksw.com/describe/?url=http%3A%2F%2Fwiki.apache.org%2Ftomcat%2FFAQ%2FCharacterEncoding

AttributesValues
described by
Title
  • FAQ/CharacterEncoding - Tomcat Wiki
comment
  • The fact is: there is no char encoding in a GET request. So an unmodified installation of Tomcat will parse the URI in a GET as ISO-8859-1 ("the Servlet spec requires it"). But a SPARQL request, for instance, requires it to be UTF-8 encoded. So it can't work!!!<br/> Tomcat people insist that their behavior is a feature. Maybe it's not a bug, but I doubt it is a feature. To get tomcat working otherwise, you have to set a parameter in the server.xml (connector, URIEncoding) What if you don't control the tomcat install? Maybe the best thing to do is to parse the parameters from request.getQueryString(). In my web apps until now, I double UTF-8 encode the params in a GET (for instance, the semanlink bookmarklet)
creation date
  • 2008-10-12
tag
is topic of
Faceted Search & Find service v1.17_git122 as of Jan 03 2023


Alternative Linked Data Documents: iSPARQL | ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3330 as of Apr 5 2024, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (30 GB total memory, 26 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software