RE: 403 Forbidden Problem on Moved Repository

David,

The crazy thing is, we have one huge repository I moved last night that
seems to not have any of these problems! We can access the server/Apache
via FQDN with no problem (i.e. don't have to use the IP). We have
Bugzilla on that machine and it is running just fine using
https://FQDN/bugzilla. Fortunately, the most critical of our
repositories seem to be okay. In addition, some people were using cached
credentials; once they dump their cached credentials, some (but not all)
of the problems seem to go away.

Rich

From: David Weintraub [mailto:qazwart_at_gmail.com]
Sent: Tuesday, July 28, 2009 11:49 AM
To: Richard Lichvar
Cc: users_at_subversion.tigris.org
Subject: Re: 403 Forbidden Problem on Moved Repository

Can you access the files via your browser? Can you access the server via
IP address? I had a similar problem where I could access the files in my
browser, but not via Subversion using the host name. I ended up putting
the Subversion host into my /etc/hosts file.

Still have no idea why, but it works.

On Tue, Jul 28, 2009 at 9:35 AM, Richard Lichvar <rlichvar_at_sainc.com>
wrote:

Not sure what is going on. Recently moved repositories are giving the
following message:

Error: Server sent unexpected return value (403 Forbidden) in response
to OPTIONS

When accessing via TortoiseSVN. Ownership of all repository files is
apache:apache (same as original repositories). This newbie must be
missing something else!

Rich Lichvar

-- 
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376329
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].