I'm not used to configure Jetty, but maybe the web-jetty.xml file can be used to set the default Content-type header charset to use ? Nicolas
On Mon, Mar 9, 2009 at 6:22 PM, John Tamplin <j...@google.com> wrote: > On Mon, Mar 9, 2009 at 12:39 PM, nicolas de loof <nicolas.del...@gmail.com > > wrote: > >> As you can see, the Jetty server does not specify any encoding in the >> content-type header, so I suppose my browser is using the platform native >> one : Windows CP1252 >> > > I believe HTTP specifies that the default is ISO-Latin-8859-1 if no charset > is specified. > > >> Is there any simple way to force Jetty to include such encoding header ? >> As GWT resources are required AFAIK to be UTF-8, what about this to be the >> default configuration for hosted mode server ? >> > > GWT resources are required to be UTF8, but that doesn't mean that all your > web-served content has to be. Ideally, it would user configurable, but I > think once you start to need to mix encodings you need to run your own > server and use -noserver. So, I would be happy with UTF8 as a default, > preferably with a way to override it for all served content. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
