You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jonas Bosson <jo...@illuminet.se> on 2002/12/12 16:56:28 UTC
Apache+mod_dav+connector dilemma
Dear tomcat wizards.
I can't get mod_dav to work since the jk connector routes all http
method calls for *.xml pages to tomcat. Any solution I can think of
requires a modification of the connectors in tomcat.
Before I proceed, I need help to decide what the best solution is:
Alt 1: Allow the connectors to act within <location> instead of for the
whole host/virtualhost so that a apache virtual folder can be shielded
from the connector. This allows for operations to be exclusive for
apache within this location.
Alt 2: Method filtering by argument to jkmount. This would allow mod_dav
to function and tomcat to serve dynamic responses only to GET, HEAD and
POST.
Alt 3: A response from tomcat (and the servlet) to the connector that it
should find the next suitable match in apache. This way we could decide
if tomcat or apache should handle the request dynamically.
... the simple solution that I am missing.
else I am ready to start modifying the connectors.
Rest regards,
--
Jonas Bosson
HomePage: http://www.illuminet.se/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Apache+mod_dav+connector dilemma
Posted by "Noel J. Bergman" <no...@devtech.com>.
Jonas,
There is a semantic conflict between DAV and dynamic content handlers if you
use the same Location. DAV would want to fetch the file, the dynamic
content handler would want to pass along the request for service. See
http://www.webdav.org/mod_dav/install.html#complex, specifically the PHP
example.
The Location solution resolves that conflict, although, I seem to recall
having to ensure that the module order was correct when I first installed
mod_dav. If you look at the LoadModule/AddModule ordering in your
httpd.conf file, you want to put mod_dav after the connector, which means it
will be checked first.
In your case, you may want to install a separate virtual host, dav.xxxx.tld,
so that you can keep the root.
--- Noel
-----Original Message-----
From: Jonas Bosson [mailto:jonas@illuminet.se]
Sent: Friday, December 13, 2002 6:05
To: Tomcat Users List
Cc: Noel J. Bergman
Subject: RE: Apache+mod_dav+connector dilemma
Hi Noel!
Yes, we use the root for dav and filtering, since unique and clear
identities/url-identifiers are very important to us.
In your conf-snipplet it seems that you bind the tomcat connector by
mime-type and then redefine the the mime-type in the 'dav' location to
avoid being captured by the connector. I cant get this to work in my
configuration. What connector / tomcat / server are you using?
Curious,
Jonas
tor 2002-12-12 klockan 22.35 skrev Noel J. Bergman:
> Jonas,
>
> Are you trying to do DAV from the root? I have a special <Location>
element
> for DAV:
>
> Alias /dav /.../htdocs
> <Location /dav/ >
> DAV On
> AddType text/plain .jsp
> AllowOverride None
> Options None
> </Location>
>
> an alternative, which I have no chosen to use, would be to define a DNS
> entry and virtual host, e.g., dav.domain.tld.
>
> --- Noel
>
> -----Original Message-----
> From: Jonas Bosson [mailto:jonas@illuminet.se]
> Sent: Thursday, December 12, 2002 10:56
> To: tomcat-user@jakarta.apache.org
> Subject: Apache+mod_dav+connector dilemma
>
>
> Dear tomcat wizards.
>
> I can't get mod_dav to work since the jk connector routes all http
> method calls for *.xml pages to tomcat. Any solution I can think of
> requires a modification of the connectors in tomcat.
>
> Before I proceed, I need help to decide what the best solution is:
>
> Alt 1: Allow the connectors to act within <location> instead of for the
> whole host/virtualhost so that a apache virtual folder can be shielded
> from the connector. This allows for operations to be exclusive for
> apache within this location.
>
> Alt 2: Method filtering by argument to jkmount. This would allow mod_dav
> to function and tomcat to serve dynamic responses only to GET, HEAD and
> POST.
>
> Alt 3: A response from tomcat (and the servlet) to the connector that it
> should find the next suitable match in apache. This way we could decide
> if tomcat or apache should handle the request dynamically.
>
>
> ... the simple solution that I am missing.
> else I am ready to start modifying the connectors.
>
> Rest regards,
> --
> Jonas Bosson
> HomePage: http://www.illuminet.se/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Apache+mod_dav+connector dilemma
Posted by Jonas Bosson <jo...@illuminet.se>.
Hi Noel!
Yes, we use the root for dav and filtering, since unique and clear
identities/url-identifiers are very important to us.
In your conf-snipplet it seems that you bind the tomcat connector by
mime-type and then redefine the the mime-type in the 'dav' location to
avoid being captured by the connector. I cant get this to work in my
configuration. What connector / tomcat / server are you using?
Curious,
Jonas
tor 2002-12-12 klockan 22.35 skrev Noel J. Bergman:
> Jonas,
>
> Are you trying to do DAV from the root? I have a special <Location> element
> for DAV:
>
> Alias /dav /.../htdocs
> <Location /dav/ >
> DAV On
> AddType text/plain .jsp
> AllowOverride None
> Options None
> </Location>
>
> an alternative, which I have no chosen to use, would be to define a DNS
> entry and virtual host, e.g., dav.domain.tld.
>
> --- Noel
>
> -----Original Message-----
> From: Jonas Bosson [mailto:jonas@illuminet.se]
> Sent: Thursday, December 12, 2002 10:56
> To: tomcat-user@jakarta.apache.org
> Subject: Apache+mod_dav+connector dilemma
>
>
> Dear tomcat wizards.
>
> I can't get mod_dav to work since the jk connector routes all http
> method calls for *.xml pages to tomcat. Any solution I can think of
> requires a modification of the connectors in tomcat.
>
> Before I proceed, I need help to decide what the best solution is:
>
> Alt 1: Allow the connectors to act within <location> instead of for the
> whole host/virtualhost so that a apache virtual folder can be shielded
> from the connector. This allows for operations to be exclusive for
> apache within this location.
>
> Alt 2: Method filtering by argument to jkmount. This would allow mod_dav
> to function and tomcat to serve dynamic responses only to GET, HEAD and
> POST.
>
> Alt 3: A response from tomcat (and the servlet) to the connector that it
> should find the next suitable match in apache. This way we could decide
> if tomcat or apache should handle the request dynamically.
>
>
> ... the simple solution that I am missing.
> else I am ready to start modifying the connectors.
>
> Rest regards,
> --
> Jonas Bosson
> HomePage: http://www.illuminet.se/
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Jonas Bosson
IllumiNet AB - From information to knowledge
HomePage: http://www.illuminet.se/
Visiting address: Narvavägen 32, 6tr Stockholm
Postal Address: Upplandsg. 85 1tr 11344 Stockholm
Office phone: +46(0)8 666 96 61
Mobile phone: +46(0)70 4217840
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Apache+mod_dav+connector dilemma
Posted by "Noel J. Bergman" <no...@devtech.com>.
Jonas,
Are you trying to do DAV from the root? I have a special <Location> element
for DAV:
Alias /dav /.../htdocs
<Location /dav/ >
DAV On
AddType text/plain .jsp
AllowOverride None
Options None
</Location>
an alternative, which I have no chosen to use, would be to define a DNS
entry and virtual host, e.g., dav.domain.tld.
--- Noel
-----Original Message-----
From: Jonas Bosson [mailto:jonas@illuminet.se]
Sent: Thursday, December 12, 2002 10:56
To: tomcat-user@jakarta.apache.org
Subject: Apache+mod_dav+connector dilemma
Dear tomcat wizards.
I can't get mod_dav to work since the jk connector routes all http
method calls for *.xml pages to tomcat. Any solution I can think of
requires a modification of the connectors in tomcat.
Before I proceed, I need help to decide what the best solution is:
Alt 1: Allow the connectors to act within <location> instead of for the
whole host/virtualhost so that a apache virtual folder can be shielded
from the connector. This allows for operations to be exclusive for
apache within this location.
Alt 2: Method filtering by argument to jkmount. This would allow mod_dav
to function and tomcat to serve dynamic responses only to GET, HEAD and
POST.
Alt 3: A response from tomcat (and the servlet) to the connector that it
should find the next suitable match in apache. This way we could decide
if tomcat or apache should handle the request dynamically.
... the simple solution that I am missing.
else I am ready to start modifying the connectors.
Rest regards,
--
Jonas Bosson
HomePage: http://www.illuminet.se/
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>