This is Chuck again from his work address (where I'm actually having the
problem)
and I've now been successful in adding myself to the mailing list
(so you no longer need to CC my home or work address - just this list).
I'm not aware of any proxy server on our network. From what little I've
read,
you have to manually set certain options in the browser (which don't
appear
to be set in any of the browsers I use); but, browser settings might
only
affect the proxy server that the browsers use - not the proxy server
that SVN might be
interacting with the make HTTP requests.
We certainly do have a firewall on our network. Obviously it
blocks/monitors incoming traffic
and at least allows HTTP requests/responses to go in/out at least on the
default HTTP port of 80
(and I assume all HTTP request verbs; but, perhaps not);
however, in my example the client and server are both on my machine
(i.e. the URL starts with
http://localhost)
Why/how would a firewall or proxy get involved?
Chuck
p.s. There are no new entries in the Apache error log. Here's the
most recent entry in the Apache access log:
127.0.0.1 - - [14/Feb/2005:23:21:01 -0500] "PROPFIND /SVN/repos
HTTP/1.1" 405 327
p.p.s. I will talk to my boss and our part time system manager. Perhaps
they can shed some light on
the proxy/firewall issue.
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Monday, February 14, 2005 11:16 PM
To: danpat@danpat.net
Cc: Subversion Users; Charles Doucette
Subject: Re: svn co gets 405 Method not allowed - how come (more
importantly, what can I do about it)?
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
---------------------------------------------------------------------
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:58:20 2005