On Friday, 7 March 2003 4:21 PM Bill Barker spake thusly:
> Once you've done the CVS check-out, it would help if you actually
> read the README that comes with it. That will tell you how to
> generate the 'configure' script.
Hi Bill,
If you actually read my message you would have noticed that
> -Original Message-
> From: Schulze Christian [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 26 March 2002 11:13 PM
> To: '[EMAIL PROTECTED]'
> Subject: Tomcat, Webapp, Apache and mod_ssl, Protocol is switching
>
>
> Hi
>
> I have a problem with my configuration of tomcat connected to
>
We are running tomcat 4.0.1 and apache 1.2.23 with mod_ssl and mod_webapp.
The line in apache/conf/httpd.conf that is used to specify the servlet
url is:
WebAppDeploy seqa conn /seqa
If I try to access this URL, everything works properly:
https://www.myserver.com/seqa/myfile.jsp
I am running Tomcat 4.0.1 connected to Apache 1.3.23 via mod_webapp 1.0
on a Redhat 7.2 system.
Directory 'a' is protected using Basic Apache authentication:
/htdocs/a
Directory 'b' is where my servlets are deployed via webapp:
/htdocs/b
I want to allow anyone access to 'b', but inside a serv
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, 23 March 2002 8:18 AM
> To: [EMAIL PROTECTED]
> Subject: Tomcat 4 getRemoteUser() with custom http
>
>
> Hi,
>
> I'm porting something off of Weblogic and onto a combination of Jboss
> and Tomca
I have a web site that uses the standard apache basic authentication
scheme.
Using mod_webapp, I have servlets served from a sub-directory in
the protected web tree. How do I cause tomcat to only serve
these servlets if the client has authenticated itself using
the standard apache authentication