>
>
> 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 cau
On 07.06.2011 21:29, Christopher Schultz wrote:
> Bernd,
>
> On 6/7/2011 2:23 PM, Lentes, Bernd wrote:
>> Christopher Schultz wrote:
>>>
>>> How did you do it? If you use >> CONTENT="text/html" />, it should override any Content-Type
>>> sent in the HTTP response headers
>
>> Yes, we used this. B
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernd,
On 6/7/2011 2:23 PM, Lentes, Bernd wrote:
Christopher Schultz wrote:
How did you do it? If you use , it should override any Content-Type
sent in the HTTP response headers
Yes, we used this. But
http://de.selfhtm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernd,
On 6/7/2011 2:23 PM, Lentes, Bernd wrote:
> Christopher Schultz wrote:
>>
>> How did you do it? If you use > CONTENT="text/html" />, it should override any Content-Type
>> sent in the HTTP response headers
>
> Yes, we used this. But
> http://
Christopher Schultz wrote:
>
> 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 CONTENT="text/html" />, it should override any Content-Type
> sent in the
-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
On 03/06/2011 10:22, André Warnier wrote:
> Pid wrote:
>> On 01/06/2011 13:13, Lentes, Bernd wrote:
>>> Andre Warnier wrote:
>>>
Your configuration of mod_jk below looks correct (except a
small detail, see JkMount).
But I must say that it is difficult to believe that the
request
Pid wrote:
> >
> >>
> >> Your configuration of mod_jk below looks correct (except a small
> >> detail, see JkMount).
> >> But I must say that it is difficult to believe that the request is
> >> actually forwarded to Tomcat, and that Tomcat then fails
> to recognise
> >> the file as a JSP page, and
Pid wrote:
On 01/06/2011 13:13, Lentes, Bernd wrote:
Andre Warnier wrote:
Your configuration of mod_jk below looks correct (except a
small detail, see JkMount).
But I must say that it is difficult to believe that the
request is actually forwarded to Tomcat, and that Tomcat then
fails to recogn
On 01/06/2011 13:13, Lentes, Bernd wrote:
> Andre Warnier wrote:
>
>>
>> Your configuration of mod_jk below looks correct (except a
>> small detail, see JkMount).
>> But I must say that it is difficult to believe that the
>> request is actually forwarded to Tomcat, and that Tomcat then
>> fails to
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
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernd,
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 fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernd,
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 c
Martin Kuen wrote:
>
> Hi Bernd,
>
> I think your colleagues forgot/didn't want to set the
> content-type in the servlet(-code)?
Yes, i also think they forgot. They are Bioinformatics and don't know much
about protocols and web servers.
>
> text/plain is apache default for anything it doesn't kn
Christopher Schulz wrote:
>
> On 6/1/2011 5:18 AM, Lentes, Bernd wrote:
> > I use JKMount, and DocumentRoot of httpd and webapps of
> tomcat are not
> > overlapping.
> >
> > [snip]
> >
> > We don't use jsp, we have servlets.
>
> Okay. Can you post your servlet code, then?
I have to ask our devel
Hi Bernd,
I think your colleagues forgot/didn't want to set the content-type in the
servlet(-code)?
text/plain is apache default for anything it doesn't know (if I recall
correctly)
If no content-type is set by the servlet, no content-type is delivered.
No content-type set by the servlet causes *
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernd,
On 6/1/2011 5:18 AM, Lentes, Bernd wrote:
> I use JKMount, and DocumentRoot of httpd and webapps of tomcat are
> not overlapping.
>
> [snip]
>
> We don't use jsp, we have servlets.
Okay. Can you post your servlet code, then?
There is no def
Igor Cimicov wrote:
>
> Are you using virtual host maybe? If so, the JkMount
> directive has to be inside VirtualHost and not in the global
> apache conf file.
>
> Igor
No.
Bernd
Helmholtz Zentrum München
Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
Ingolstädter Landstr. 1
85764
Are you using virtual host maybe? If so, the JkMount directive has to be
inside VirtualHost and not in the global apache conf file.
Igor
On Jun 1, 2011 10:14 PM, "Lentes, Bernd"
wrote:
Andre Warnier wrote: > > Your configuration of mod_jk below looks correct
(except a > small detail,...
The con
Andre Warnier wrote:
>
> Your configuration of mod_jk below looks correct (except a
> small detail, see JkMount).
> But I must say that it is difficult to believe that the
> request is actually forwarded to Tomcat, and that Tomcat then
> fails to recognise the file as a JSP page, and returns it as
Pid wrote:
>
> On 01/06/2011 10:55, Lentes, Bernd wrote:
> > lrwxrwxrwx 1 root root 20 Apr 18 16:33 webapps ->
> /srv/tomcat6/webapps/
>
> What is in the webapps dir? A directory called 'mouseidgenes'?
>
Yes.
> If so, what is the file tree in that directory?
>
vm53200-12:~ # l /srv/tomcat
On 01/06/2011 10:55, Lentes, Bernd wrote:
> lrwxrwxrwx 1 root root 20 Apr 18 16:33 webapps -> /srv/tomcat6/webapps/
What is in the webapps dir? A directory called 'mouseidgenes'?
If so, what is the file tree in that directory?
What is "/mouseidgenes/InputData"? Is it a servlet or a JSP?
p
On 01/06/2011 11:04, André Warnier wrote:
>> JkMount /mouseidgenes/* appl01
>
> This will forward a request like "/mouseidgenes/index.jsp", but will not
> forward the URL "/mouseidgenes". You may want to add
> JkMount /mouseidgenes appl01
There is a syntax method to address this situat
Lentes, Bernd wrote:
Charles Caldarale wrote:
when talking with a web browser directly to tomcat (port 8080), the
web page is shown correctly.
Are you sure the original request on port 80 is actually
making it through httpd all the way to Tomcat? The symptoms
you're reporting are characterist
Andre Warnier wrote:
> Lentes, Bernd wrote:
> > Hi,
> >
> > first, i'm new to tomcat and i'm not a java developer.
>
> You have all my sympathy.
>
> > My collegues developed a web application i have to deploy
> now. I'm using tomcat6 on a sles 11 sp1 box.
> > I configured a httpd (apache 2.2.10) i
. Ok, that's the reason why i see the source code. Can i
> > configure the content-type which is delivered by tomcat ? I tried
> > using mod_mime_magic on httpd, but this module just helps
> specifying
> > the content-type of static files. Our content is dynamic.
&
Charles Caldarale wrote:
>
> > when talking with a web browser directly to tomcat (port 8080), the
> > web page is shown correctly.
>
> Are you sure the original request on port 80 is actually
> making it through httpd all the way to Tomcat? The symptoms
> you're reporting are characteristic of
ing something in Tomcat won't help.
I tried using mod_mime_magic on httpd,
but this module just helps specifying the content-type of static files. Our content is
dynamic.
Yes, and that is like putting new paint on top of schimmel.
You should fix the configuration first.
If you wa
e the content-type which is delivered by
> tomcat ? I tried using mod_mime_magic on httpd, but this module just
> helps specifying the content-type of static files. Our content is
> dynamic.
First, let's make sure that the .jsp files are being executed. If not,
you are chasing the
> From: Lentes, Bernd [mailto:bernd.len...@helmholtz-muenchen.de]
> Subject: RE: specifying the content-type
> when talking with a web browser directly to tomcat (port 8080),
> the web page is shown correctly.
Are you sure the original request on port 80 is actually making it th
pe which is delivered by tomcat ? I tried using
> mod_mime_magic on httpd, but this module just helps
> specifying the content-type of static files. Our content is dynamic.
>
> Thanks in advance.
>
>
> Bernd
>
appendix:
when talking with a web browser directly to tomcat (po
magic on
httpd, but this module just helps specifying the content-type of static files.
Our content is dynamic.
Thanks in advance.
Bernd
--
Bernd Lentes
Systemadministration
Institut für Entwicklungsgenetik
HelmholtzZentrum münchen
bernd.len...@helmholtz-muenchen.de
phone: +49 89 3187 1241
fax
36 matches
Mail list logo