-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lentes,
On 6/7/2011 11:36 AM, Lentes, Bernd wrote:
> first we tried to set the content-type in the ...
> section in the html file. That didn't work.
How did you do it? If you use , it should override any Content-Type sent in the
HTTP response heade
Hi,
first we tried to set the content-type in the ... section in the
html file. That didn't work.
Our developers try now to use the response.setContentType("text/html"); method
to configure the content-type in the HTTP-Header.
What i also found out is that you can use a defaulttype directive
Christopher Schultz wrote:
...
For whatever reason, httpd wants to send a
content-type and makes the default (text/plain) explicit for you if none
is present.
..
per RFC 2616 :
7.2.1 Type
...
Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field
defining t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 6/2/2011 4:02 PM, André Warnier wrote:
> As others already mentioned, setting the proper header at the Tomcat
> webapp level would be the best solution (and a "clean" application
> should do that anyway).
+1
The lack of a header being set
Lentes, Bernd wrote:
Andre Warnier wrote:
On 6/1/2011 1:04 PM, Lentes, Bernd wrote:
Okay. Can you post your servlet code, then?
I have to ask our developers.
Okay.
There is no default Content-Type for HTTP responses, so
getting a response directly from Tomcat might cause the
browser to aut
Andre Warnier wrote:
>
> On 6/1/2011 1:04 PM, Lentes, Bernd wrote:
>>> Okay. Can you post your servlet code, then?
>> I have to ask our developers.
>
> Okay.
>
>>> There is no default Content-Type for HTTP responses, so
>>> getting a response directly from Tomcat might cause the
>>> browser to au
