Commit Fails - 200 OK

[Darrell Burgan <db...@agency.com>]

Hello all, I have a strange SVN problem.  We're using TortoiseSVN and the SVN server under Apache.  Everything works great when I'm on my local network or VPN'd into that network.  We opened up our firewall to allow two specific IP address ranges in to our SVN server, so that I can access SVN from my client's networks.  I am able to read from the SVN server but am unable to write anything, but *only* when I'm on the client's network!
 
For example, from the client's site I can do an svn update with no problems.  If I attempt an svn commit however, I get an error message like this:
 
Error    Commit failed (details follow)
Error   MKACTIVITY of '/svn/clientname/!svn/084dffd4-b974-8dcd-a990e842b61c': 200 OK (http://servername)
 
The error is always "200 OK".  To make matters worse, for about 10 minutes after one of these errors, I'm unable to connect to the SVN server in any way from the client's network, after which I'm able to resume read-only access to the SVN server.  Of course, while I'm doing this, people on my local network back in Dallas are having no problems accessing the SVN server.  This *only* happens from the remote network.
 
Does this ring any bells with anyone?  Does SVN have to be able to call back to the IP address of the client in some way?  E.g. could my client's firewall somehow be preventing SVN from talking back to TortoiseSVN?
 
I've googled this prob and searched the mailing lists to no avail - seems I'm the only person having this trouble.  Any help anyone could provide would be greatly appreciated!
 
Darrell Burgan
Senior Technical Director
Agency.com
7850 N. Belt Line Road, 4th Floor
Irving, Texas 75063
dburgan@agency.com
214.564.4450



___________________________________________________
This e-mail is intended only for the named person or entity to which
it is addressed and contains valuable business information that is 
privileged, confidential and/or otherwise protected from disclosure. 
Dissemination, distribution or copying of this e-mail or the 
information herein by anyone other than the intended recipient, or 
an employee or agent responsible for delivering the message to the 
intended recipient, is strictly prohibited. All contents are the 
copyright property of Agency.com Ltd., its affiliates or a client of 
such agencies. If you are not the intended recipient, you are 
nevertheless bound to respect the worldwide legal rights of 
Agency.com, its affiliates and its clients. We require that 
unintended recipients delete the e-mail and destroy all electronic 
copies in their system, retaining no copies in any media. If you
have received this e-mail in error, please immediately notify us via 
e-mail to disclaimer@agency.com. We appreciate your cooperation.

We make no warranties as to the accuracy or completeness of this 
e-mail and accept no liability for its content or use. Any opinions 
expressed in this e-mail are those of the author and do not 
necessarily reflect the opinions of Agency.com or any of its 
affiliates.

Re: Commit Fails - 200 OK

[Eric Lemes <er...@gmail.com>]

Hello Darrell,

It may sounds strange... but if you're in a Windows SVN Server, it can solve
your problem.

If the repository name in the checkout URL is different (case-sensitive
issue) and your server uses SVN Access File, you will read any info, but
your commit's will not work. Try to relocate your working copy with correct
repository name. Remeber, TortoiseSVN remembers the checkout URL's (and it
will remember the wrong name), you will need to type it twice.


Eric

On 6/20/06, Darrell Burgan <db...@agency.com> wrote:
>
>  Hello all, I have a strange SVN problem.  We're using TortoiseSVN and the
> SVN server under Apache.  Everything works great when I'm on my local
> network or VPN'd into that network.  We opened up our firewall to allow two
> specific IP address ranges in to our SVN server, so that I can access SVN
> from my client's networks.  I am able to read from the SVN server but am
> unable to write anything, but *only* when I'm on the client's network!
>
> For example, from the client's site I can do an svn update with no
> problems.  If I attempt an svn commit however, I get an error message like
> this:
>
> Error    Commit failed (details follow)
> Error   MKACTIVITY of
> '/svn/clientname/!svn/084dffd4-b974-8dcd-a990e842b61c': 200 OK (
> http://servername) <http://servername%29>
>
> The error is always "200 OK".  To make matters worse, for about 10 minutes
> after one of these errors, I'm unable to connect to the SVN server in any
> way from the client's network, after which I'm able to resume read-only
> access to the SVN server.  Of course, while I'm doing this, people on my
> local network back in Dallas are having no problems accessing the SVN
> server.  This *only* happens from the remote network.
>
> Does this ring any bells with anyone?  Does SVN have to be able to call
> back to the IP address of the client in some way?  E.g. could my client's
> firewall somehow be preventing SVN from talking back to TortoiseSVN?
>
> I've googled this prob and searched the mailing lists to no avail - seems
> I'm the only person having this trouble.  Any help anyone could provide
> would be greatly appreciated!
>
>
> Darrell Burgan
> Senior Technical Director
> Agency.com
> 7850 N. Belt Line Road, 4th Floor
> Irving, Texas 75063
> dburgan@agency.com
> 214.564.4450
>
> ___________________________________________________
> This e-mail is intended only for the named person or entity to which
> it is addressed and contains valuable business information that is
> privileged, confidential and/or otherwise protected from disclosure.
> Dissemination, distribution or copying of this e-mail or the
> information herein by anyone other than the intended recipient, or
> an employee or agent responsible for delivering the message to the
> intended recipient, is strictly prohibited. All contents are the
> copyright property of Agency.com Ltd., its affiliates or a client of
> such agencies. If you are not the intended recipient, you are
> nevertheless bound to respect the worldwide legal rights of
> Agency.com, its affiliates and its clients. We require that
> unintended recipients delete the e-mail and destroy all electronic
> copies in their system, retaining no copies in any media. If you
> have received this e-mail in error, please immediately notify us via
> e-mail to disclaimer@agency.com. We appreciate your cooperation.
>
> We make no warranties as to the accuracy or completeness of this
> e-mail and accept no liability for its content or use. Any opinions
> expressed in this e-mail are those of the author and do not
> necessarily reflect the opinions of Agency.com or any of its
> affiliates.
>
>