y the original
message without making a copy. Thank you.
- Original Message -
From: "Evan J " <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Monday, August 21, 2006 9:28 AM
Subject: Re: JkMount and Context path
> Martin,
>
> Indeed, I had the
Martin,
Indeed, I had the same setting with the standalone Tomcat webserver
and the configuration your mention would work properly as it expected.
As I had mentioned in earlier posts to this thread, I do not have a
reason to utilize a third party webserver. At this point I am just
trying various
mcat run standalone?
>> M-
>> *************
>> This email message and any files transmitted with it contain
confidential
>> information intended only for the person(s) to whom this email message
is
>> addressed. If y
Uhh! Ok, that's what I wanted to hear and it is evident that Context's
path is being ignored but why HTTP 400? Anyway, I do not believe the
"name" of context file has any bearing on the URI that must be
specified.
http://tomcat.apache.org/tomcat-5.5-doc/deployer-howto.html says,
"If a Context De
Evan J wrote:
> conf/enginename/vh.host.com/myapp.xml:
>
>docBase="/myapp"...>
Ahh. Light dawns. It wasn't clear (to me at least) that you were using
a context.xml file. I had assumed you were specifying the context
inside server.xml. Using the configuration above the path will be
Ok, that's what I had expected,
http://vh.host.com/someuri/eservlets/myservlet, but in reality, such
URL would produce HTTP 400 which has been puzzling me and I had
assumed I had some misunderstanding of something. But the weird thing
is http://vh.host.com/myapp/eservlets/myservlet works flawlessl
Evan J wrote:
> Yes, I understand that perfectly. What I am asking is what if we
> include a web application Context path, that is path="someuri"...>. Of course, JkMount /*/eservlet/* would relay all
> the request with mywebapp/eservlet/* from Apache to Tomcat -- I am
> aware of that. Now if we se
telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: "Evan J " <[EMAIL PROTECTED]>
To: "Tomcat Users List" ; "Martin Gainty" <[EMAIL
PROTECTED]>
Sent: Sunday, August 20, 2006 1:15 PM
Su
gt;
To: "Tomcat Users List" ; "Martin Gainty" <[EMAIL
PROTECTED]>
Sent: Sunday, August 20, 2006 1:15 PM
Subject: Re: JkMount and Context path
> Martin,
>
> I have the documents and I'm aware the difinition of Context path and
> from what you have p
one or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: "Evan J " <[EMAIL PROTECTED]>
To: "Tomcat Users List" ; "Martin Gainty" <[EMAIL
PROTECTED]>
Sent: Sunday, August 20, 2006 1:01 AM
Subject: Re:
or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: "Evan J " <[EMAIL PROTECTED]>
To: "Tomcat Users List" ; "Martin Gainty" <[EMAIL
PROTECTED]>
Sent: Sunday, August 20, 2006 1:01 AM
Subject: Re: J
Ok, your answer just recaps everything that is needed to run
Apache-jk_mod-Tomcat but does not answer my question. What if in your
setting, you have set Context path, what would be the consequences?
How are the servlets then are accessed? Is it required to include
Context path in the uri ending to
/*httpd.conf
JkMount maps all JSP (*.jsp) to ajp13
*/
e.g.
httpd.conf
JkMount /*.jsp ajp13
/*map ajp13 to your webapp docRoot /var/tomcat4/webapps/domain1
ServerName domain1.com
ServerAlias www.domain1.com
DocumentRoot /var/tomcat4/webapps/domain1
JkMount /* ajp13
/*server.xml
I've a question regarding the way jk_mod relays requests to Tomcat
servlets. If I have set my virtualhost to supposedly send requests
with such JkMount directive URL prefix, /serve/* and /serve/*.jsp,
then I take it, the only way for jk_mod relays requests for this
virtualhost to Tomcat web applic
14 matches
Mail list logo
