Similar problem here, if all the content comes from Tomcat it works fine.
Servlet html that referenced image urls on apache caused apache to die. 
--


    Hi.
    I have the same problem as you.
    Tomcat4.0 and mod_webapp with SSL it seems to be a taboo topic.
There isn't any information.

  

[EMAIL PROTECTED] wrote:

>Hi all
>
>Does any one have an idea how to make mod_webapp work properly with a
apache
>mod_ssl vitual server?
>
>Here is the scenario:
>
>I have a web application that can run in either native tomcat or with
apache
>as a fron end. I use mod webapp to provide a mapping of the application to
>the apache server (ala old style JServ) and then it talks to tomcat on port
>8008. I was under the impression that this is how it works:
>
>apache gets a request for a "mapped" web application so that it looks like
>this: https://somehost/app?<appdata> on the client end, picks up the
>app-data and then shoves it down port 8008 on localhost (thats where the
>warp connector is told to go) and then returns the data to the client via
>SSL. SO it would look like this:
>
>client <--- HTTPS  ---> Apache <-- warp connection to locahost:8008 -->
>tomcat
>
>Is this possible or am I better of running native tomcat on port 443 and
not
>bother with apache at all?
>
>regards
>Tomasz Ciolek
>
>--
>Tomasz M. Ciolek
>Systems Administrator - CSIRO Entomology
>Phone: 02-62464391 * Fax: 02-62464000
>
>
>--
>To unsubscribe:   <mailto:[EMAIL PROTECTED]>
>For additional commands: <mailto:[EMAIL PROTECTED]>
>Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>
>

--
-------------------------------------------------
Gabriel Lopez Millan - Grupo ANTS-CIRCuS
Facultad de Informática
Universidad de Murcia (España) Tfo: +34 968367645




--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
Confidentiality Caution and Disclaimer

This message and/or any attachment thereto ("the message") 
contains privileged and confidential information intended 
only for the recipient named above.  
If you are not the intended recipient of this message, 
please erase it permanently once you have notified the 
sender, per return e-mail, that you have received the 
message in error.
Unless the sender is duly authorised by either the Telesure 
Group, or any of its subsidiary companies or I.S Services 
("the Group") to send this message and unless the content 
of this message is also duly authorised by the Group, any 
views expressed in this message are those of the individual 
sender and the Group will not accept liability therefore, 
nor for any consequential damage arising therefrom.
Any recipient of an unacceptable communication, a chain 
letter or offensive material of any nature is requested 
to report it to [EMAIL PROTECTED]

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to