[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn co gets 405 Method not allowed - how come (more importantly, what can I do about it)?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-15 05:15:50 CET

On Feb 14, 2005, at 10:04 PM, Daniel Patterson wrote:

>> Anonymous atucker dchase spowers bferber cdoucette vss_migration
>> ...
>> Require valid-user
>>
>> C:\MySVNwd>svn co http://localhost:8080/SVN/repos/
>> svn: PROPFIND request failed on '/SVN/repos'
>> svn: PROPFIND of '/SVN/repos': 405 Method Not Allowed
>> (http://localhost:8080)
>>
>> Please tell me how to get this working.
>
> You've configured it to require a valid user, but you haven't
> supplied a username on the command line. Your users don't
> need passwords, but they need names.
>
> Try:
>
> svn co http://localhost:8080/SVN/repos/ --username atucker
>

Daniel: passing --username doesn't change anything here. The client
never "pushes" authentication at the server. The server only "pulls"
authentication if it decides it needs it. The --username option just
sets up a name on stand-by, to be used *only* if the server asks.
Either the server asks, or it doesn't... the client can't affect that.
If the server asks, and --username isn't present, then the client will
prompt the user anyway. So the fact that he wasn't prompted means the
server never asked for authentication... and thus --username won't
change a thing.

The 405 error that Charles is seeing, however, is most often caused by
a web proxy blocking WebDAV http requests (like PROPFIND). That's most
likely the problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 15 05:19:23 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.