RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

2002-06-19 Thread GOMEZ Henri

The question is :

What should do http server ?

forward to tomcat /index.jsp and if it fail, try next
to forward /index.vm ?

-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .) 
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



-Original Message-
From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 19, 2002 1:19 AM
To: Tomcat Dev List
Subject: RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36


It doesn't work in either case. In this case it should be index.vm,
since that's the file that exists in the directory.

Bojan

On Tue, 2002-06-18 at 19:58, GOMEZ Henri wrote:
 question.
 
 Should mod_jk forward to tomcat index.jsp or index.vm ?
 
 -
 Henri Gomez ___[_]
 EMAIL : [EMAIL PROTECTED](. .) 
 PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
 PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 
 
 
 
 -Original Message-
 From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
 Sent: Monday, June 17, 2002 1:11 PM
 To: Tomcat Dev List
 Subject: index.*: mod_jk 1.2.0 vs. Apache 2.0.36
 
 
 I've submitted a bug regarding this (9913) since it still 
appears to be
 there in the above combo.
 
 This should be very simple to test (you just whack an index.jsp in a
 directory), so if someone can confirm that my configuration is
 brain-dead (because this is such an unlikely bug :-), that would be
 nice.
 
 Bojan
 
 
 --
 To unsubscribe, e-mail:   
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: 
 mailto:[EMAIL PROTECTED]
 
 
 
 --
 To unsubscribe, e-mail:   
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]
 



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

2002-06-19 Thread Bojan Smojver

Yes, pretty much. I'm guessing that Apache will try it's own page types
first (index.shtml, index.html etc.) and if if doesn't find any, pass
the request to Tomcat (through mod_jk) for index.jsp and then index.vm
(in that order, since that's how it's specified in DirectoryIndex).

Just for the record, the server displayed the content of the directory
(this is on the test machine where that's allowed).

When I put explicit URL in the address field of the brower (e.g.
http://www.testsite.dev/index.vm) it does work (i.e. Tomcat picks up the
servlet that handles *.vm pages etc.).

Bojan

On Wed, 2002-06-19 at 18:23, GOMEZ Henri wrote:
 The question is :
 
 What should do http server ?
 
 forward to tomcat /index.jsp and if it fail, try next
 to forward /index.vm ?
 
 -
 Henri Gomez ___[_]
 EMAIL : [EMAIL PROTECTED](. .) 
 PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
 PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 
 
 
 
 -Original Message-
 From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, June 19, 2002 1:19 AM
 To: Tomcat Dev List
 Subject: RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36
 
 
 It doesn't work in either case. In this case it should be index.vm,
 since that's the file that exists in the directory.
 
 Bojan
 
 On Tue, 2002-06-18 at 19:58, GOMEZ Henri wrote:
  question.
  
  Should mod_jk forward to tomcat index.jsp or index.vm ?
  
  -
  Henri Gomez ___[_]
  EMAIL : [EMAIL PROTECTED](. .) 
  PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
  PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 
  
  
  
  -Original Message-
  From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
  Sent: Monday, June 17, 2002 1:11 PM
  To: Tomcat Dev List
  Subject: index.*: mod_jk 1.2.0 vs. Apache 2.0.36
  
  
  I've submitted a bug regarding this (9913) since it still 
 appears to be
  there in the above combo.
  
  This should be very simple to test (you just whack an index.jsp in a
  directory), so if someone can confirm that my configuration is
  brain-dead (because this is such an unlikely bug :-), that would be
  nice.
  
  Bojan
  
  
  --
  To unsubscribe, e-mail:   
  mailto:[EMAIL PROTECTED]
  For additional commands, e-mail: 
  mailto:[EMAIL PROTECTED]
  
  
  
  --
  To unsubscribe, e-mail:   
 mailto:[EMAIL PROTECTED]
  For additional commands, e-mail: mailto:[EMAIL PROTECTED]
  
 
 
 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]
 
 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]
 



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

2002-06-19 Thread GOMEZ Henri

Yes, pretty much. I'm guessing that Apache will try it's own page types
first (index.shtml, index.html etc.) and if if doesn't find any, pass
the request to Tomcat (through mod_jk) for index.jsp and then index.vm
(in that order, since that's how it's specified in DirectoryIndex).

Just for the record, the server displayed the content of the directory
(this is on the test machine where that's allowed).

When I put explicit URL in the address field of the brower (e.g.
http://www.testsite.dev/index.vm) it does work (i.e. Tomcat 
picks up the
servlet that handles *.vm pages etc.).

Hum, I think the problem should be easier to detect (I hope so)

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

2002-06-19 Thread Bojan Smojver

On Wed, 2002-06-19 at 18:45, GOMEZ Henri wrote:

 Hum, I think the problem should be easier to detect (I hope so)

Yeah, I agree. I actually think that my configuration could be screwed
somewhere, somehow (although I don't see how) because almost all Apache
2.0.x/Tomcat 3.3.x users would run into this kind of problem...

Bojan


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

2002-06-19 Thread GOMEZ Henri

 Hum, I think the problem should be easier to detect (I hope so)

Yeah, I agree. I actually think that my configuration could be screwed
somewhere, somehow (although I don't see how) because almost all Apache
2.0.x/Tomcat 3.3.x users would run into this kind of problem...

Not sure. In fact many site make use of :

JkMount /examples/* ajp13

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: index.*: mod_jk 1.2.0 vs. Apache 2.0.36

2002-06-18 Thread GOMEZ Henri

question.

Should mod_jk forward to tomcat index.jsp or index.vm ?

-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .) 
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



-Original Message-
From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 17, 2002 1:11 PM
To: Tomcat Dev List
Subject: index.*: mod_jk 1.2.0 vs. Apache 2.0.36


I've submitted a bug regarding this (9913) since it still appears to be
there in the above combo.

This should be very simple to test (you just whack an index.jsp in a
directory), so if someone can confirm that my configuration is
brain-dead (because this is such an unlikely bug :-), that would be
nice.

Bojan


--
To unsubscribe, e-mail:   
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: 
mailto:[EMAIL PROTECTED]



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]