RE: Problem: Authorization Failed and 403 Forbidden

Hi,

   Finally found the solution, well explained here:
http://svn.haxx.se/dev/archive-2006-01/0688.shtml, typical problem
related to case sensitiveness. I didn't think about this problem because
updates and checkouts worked, but commits didn't. I supposed all
operations should work the same related to permissions.

Thank you,

-----Mensaje original-----
De: Lieven Govaerts [mailto:lgo@mobsol.be]
Enviado el: jueves, 30 de marzo de 2006 20:30
Para: Aguirre Perez, Jose Manuel [SBD]; users@subversion.tigris.org
Asunto: RE: Problem: Authorization Failed and 403 Forbidden

Hi,

Maybe you can provide us some more - specific - information:

What does your apache error log say?

Which type of authentication do you use?

Do you use path-based authorization?

Can you reproduce it?

Lieven.

        
________________________________

        From: Aguirre Perez, Jose Manuel [SBD]
[mailto:jmaguirre@mailext.com]
        Sent: donderdag 30 maart 2006 20:04
        To: users@subversion.tigris.org
        Subject: Problem: Authorization Failed and 403 Forbidden

        Hi all and thanks in advance,

         We have recently upgraded from Subversion 1.2.1 to Subversion
1.3 and have the following problem:

            Some users cannot commit to some repositories, they get the
following error:

        svn: Commit failed (details follow):

            svn: Commit failed (details follow):

        svn: MKACTIVITY of '/in_svn/SGOGNCOM/!svn/act/0000010a4ba526a0':
authorization failed ('http://repsvn.intranet.gasnatural.com')

        OR

        Error: MKACTIVITY of
'/in_svn/SGOGNCOM/!svn/act/07574d14-fb43-a54c-a447-0b8f5854bfe6': 403
Forbidden (http://repsvn.intranet.gasnatural.com)

        Other users can commit to those repositories without problem,
checking out a completely new local copy doesn't work. Configuration on
server side appears to be correct.

        We just run the installation program downloaded from subversion
site to upgrade the server, so apache remains the same.

        We are using apache httpd 2.0.54 and subversion 1.3.0 on server
on a windows 2003 server. On client side we use Subclipse and Tortoise,
we get the same error with both. I have searched in forums, but don't
find any solution.

        NOTE: no ssl is being used.

        Any idea would be of great help.

        Thanks in advance

         
Received on Fri Mar 31 10:20:45 2006