Re: Index files ( was RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Tue, 23 Jul 2002 [EMAIL PROTECTED] wrote: > Date: Tue, 23 Jul 2002 09:34:18 -0700 (PDT) > From: [EMAIL PROTECTED] > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: Tomcat Developers List <[EMAIL PROTECTED]> > Subject: Re: Index files ( was RE: cvs commit: > jakarta-tomcat-conn

Re: Index files ( was RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Tue, 23 Jul 2002, Craig R. McClanahan wrote: > > It's the index.jsp that worries me - combined with precompile jsps. > > > > That could be an extremely common case - and will fail with the > > current implementation. > > > > As a workaround, why don't you just include the JSP source files in

Re: Index files ( was RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Mon, 22 Jul 2002 [EMAIL PROTECTED] wrote: > > It's the index.jsp that worries me - combined with precompile jsps. > > That could be an extremely common case - and will fail with the > current implementation. > As a workaround, why don't you just include the JSP source files in the war anywa

Index files ( was RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Mon, 22 Jul 2002, Craig R. McClanahan wrote: > In Servlet 2.4 (Community Draft 2), it looks like the language in Section > 9.10 that describes this hasn't changed. The basic rule is that you > combine the "partial URLs" specified in the welcome file list to the > incoming request for a "direc

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Sun, 21 Jul 2002 [EMAIL PROTECTED] wrote: > On Mon, 22 Jul 2002, Bojan Smojver wrote: > > > > it can already map any URI. All it has to do is: > > > - for each index: > > > > Just reading the algorithm and thinking about the implementation of it. Some of > > Well, don't take it as an algorit

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Sun, 21 Jul 2002, Bill Barker wrote: > At the moment, the servlet-mapping issue is somewhat of a red-herring, since > only 3.3.2-dev supports it (and even there, it is disabled by default). For > now, mod_jk(2) might as well assume that the physical jsp/vm file is there, > since Tomcat requir

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Mon, 22 Jul 2002, Bojan Smojver wrote: > > it can already map any URI. All it has to do is: > > - for each index: > > Just reading the algorithm and thinking about the implementation of it. Some of Well, don't take it as an algorithm - there are many other things to consider. > > > The

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Mon, 22 Jul 2002, Bojan Smojver wrote: > Quoting [EMAIL PROTECTED]: > > > > Are you referring here to mod_jk2 only or both mod_jk 1.2.0 and > > mod_jk2? > > > > I think it could be done for jk2 ( but not easy ). I'm not sure > > about 1.2 - just forwarding and letting tomcat handle > > it is

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Mon, 22 Jul 2002, Bojan Smojver wrote: > > You don't need to ask tomcat - jk should have all the mappings, and > > it can already map any URI. All it has to do is: > > - for each index: > > -- concatenate with the current uri > > -- do the jk mapping ( or internal redirect if you use

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Mon, 22 Jul 2002, Bojan Smojver wrote: > Which is how it used to be in the old code anyway. And that means that > DirectoryIndex should not be used if you don't have physical files in the right > places (with the current patch level in mod_jk 1.2.x for Apache 2) or in virtual > places (with th

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On 22 Jul 2002, Bojan Smojver wrote: > If there is no physical file, then nothing will get done by the patch at > all (since r->finfo.filetype is 0). It won't affect mod_dir's old > behaviour at all. I'm not sure how that changes things... My question was: if you have a precompiled index.jsp, th

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Mon, 2002-07-22 at 01:39, [EMAIL PROTECTED] wrote: > I think Mladen chose the wrong example, but he is right. > > Think about the case when pre-compiled JSPs are used. In this case > index.jsp is converted to a servlet - in the deployed application > there is no 'index.jsp' file, just a servl

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

sage- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, July 21, 2002 5:47 PM > > To: Tomcat Developers List > > Subject: RE: cvs commit: > > jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c > > > > > > On S

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

Since I didn't really like my original 'fix' for mod_jk 1.2.0 situation (bug 9913), I tried this approach, but it seems to make no difference whatsoever... The content of the directory is being served rather then default pages. Bojan On Fri, 2002-07-19 at 01:15, [EMAIL PROTECTED] wrote: > mturk

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

On Fri, 2002-07-19 at 01:15, [EMAIL PROTECTED] wrote: > mturk 2002/07/18 08:15:00 > > Modified:jk/native2/server/apache2 mod_jk2.c > Log: > Fix the bug 10789 caused by hook order. Thanks Mladen. Bojan -- To unsubscribe, e-mail: For additional comma

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2mod_jk2.c

You should also have a look to jakarta-commons-sandbox/daemon/src/native/unix/native/location.c for the defaultVM_PATH possible values. (The variable is named location_jvm_default there). [EMAIL PROTECTED] wrote: > costin 2002/06/01 08:40:09 > > Modified:jk/native2/common jk_vm_de