On 2004-11-18 01:50-0600, Andrew Leeper wrote:
> #Your WebDAV server sees your move, copy commands to be come as from
> #different namespace (domain names), and refuces to do the operations.
> #This happens because your are mixing https and name based virtual
> #domains, which don mix well:
First of, a disclaimer, so you know how valuable my words are or not.
I had once a similar problem, and I found one posting on the WebDAV
mailing list which explained the reason behind this problem. So I am
not any way a WebDAV expert.
> Do you mean that because I'm using both port 80 and 443
> for the same virtual host directive it's messing it up? If so,
> I tried to remove the port 80 directive and use only 443 and
> still have the same result.
I think that the problem is following:
You have a hostname www.my.com for your domain, and you have
svn.my.com on your https virtual host definition.
However by the nature of https, the host name of connection is
www.my.com at the time of initial connection, because the server has
no means to check the virtual host settings when connection comes in.
Please read following FAQ item, it makes much more sense than above:
After that your setup uses svn.my.com as host name, so when MOVE or
COPY commands came in, your system sees you are moving or copying from
different namespaces (from www.my.com to svn.my.com) and refuses to do
it. For this reason server answers Bad Gateway.
> I also moved this virtual host to the top of the virtual host
> directives which should make it the default location on the
> server. I still have the same result with this as well.
If you could, do an IP based virtual hosting, it works, and is fairly
easy to set up. Or devove a special path for your subversion stuff, i.e.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Nov 18 09:12:06 2004