On Thursday 30 August 2001 01:10, jean-frederic clere wrote:
> Ryan Bloom wrote:
> > Hi everybody,  I'm new to the list, but for anybody who doesn't know me,
> > I have been pretty active on httpd 2.0.  I decided to port mod_webapp
> > last week, and Pier committed the code for me, but the build system isn't
> > there, so I am posting the build system now.
> >
> > This is currently working, although there seems to be some strangeness
> > when Tomcat responds to mod_webapp.  I'll be looking into that over the
> > next few days. I hope to be more active as time permits.  :-)
> >
> > The Makefile.in should be placed in
> > jakarta-tomcat-connectors/webapp/apache-2.0
>
> Hi Ryan,
>
> I committed some code some hours before... I will try to merge the two.
> I am detecting  Apache version using apxs thru the following code:
> +++
>     dnl test apache version (from mod_jk)
>     $RM -rf test
>     $APXS -n test -g
>     APA=`grep STANDARD20 test/mod_test.c`
>     if  ${TEST} -z "$APA" ; then
>       TARGET="${SRCDIR}/apache-1.3"
>       makefile="apache-1.3/Makefile"
>     else
>       TARGET="${SRCDIR}/apache-2.0"
>       makefile="apache-2.0/Makefile"
>     fi
> +++
> Any comment? - I am using the same in mod_jk -

Doesn't this needlessly create a new directory on the machine?  And, it doesn't
clean that dir until the next time you try to configure.  At the very least,
we should execute the '$RM -rf test' command after the grep.  It would actually
be possible to just do 'grep STANDARD20 $APXS'.  This is because
the perl script actually has a copy of the module in it.  That is probably the
cleanest solution.

> I have also noted strange things mod_webapp always returns 500.
> It seems the request is mapped (wam_match) correctly but the handler
> (wam_invoke) is not called.
> What is the problem you have detected?

It looks like when Tomcat returns a 302 through mod_webapp, we are
redirected to a strange port.  I haven't even begun to look at it yet, but I
am hoping to have time either today or tomorrow.

Ryan
______________________________________________________________
Ryan Bloom                              [EMAIL PROTECTED]
Covalent Technologies                   [EMAIL PROTECTED]
--------------------------------------------------------------

Reply via email to