> > > If the server isn't sensing and interpreting the character set header
> > correctly, or if the browser is sending something wrong or weird,
> > that could easily cause this sort of trouble.
> > It seems to happen after one enters international chars in the meta
> > data...
> > This causes Tomcat to send a wrong
> > <meta http-equiv="Content-Type" content="text/html; charset=XXXX????">
> > back...
> Can we actually see what's happening? I'd like to know what the charset
> being passed back actually is. My understanding is that the correct
> meta tag should be written into every XHTML file passed to the browser
> (as defined by the DSpace code); does this charset define the scope for
> the form fields on the page? It seems likely that the problem is when
> the browser passes back the form fields, that it's not correctly
> attaching the content type information, which wouldn't be detectable by
> looking at the meta tags of the loaded page.
> Have you tried using the RequestDumperValve in the tomcat setup? I will
> have a go at this and see what I can find.
I have finally had a chance to look at this, and attach the
RequestDumperValve's output during a failed edit.
An important line is:
So the request comes in containing the incorrect characters. Therefore
it's at least not a DSpace problem, and seems unlikely to be a Tomcat
Nonetheless we have now experienced this error in the following
1) When the administrator session times out, using IE
2) When the administrator session times out, using Firefox
3) When the administrator session is still valid, using Firefox
> > ... but what is the fix? It has got to be (?) a tweak to the Tomcat
> > settings or response as we have little control over the browser (?)
> Can we force Tomcat to always use a particular charset, or better still,
> tell a particular webapp to always use a particular charset (e.g. in
The HTTP headers say that:
Which seems pretty reasonable. If we're using UTF-8 there ought not to
be a problem.
I was kind of hoping that we would find an obvious flaw in the request,
but since the last time I looked at this the problem has manifested in a
way previously unnoticed (3), and doesn't have an obvious fix.
Richard Jones |
Overingeniør | Senior Engineer
Universitetsbiblioteket i Bergen | University of Bergen Library
t: +47 55 58 25 37