Glenn, do you have any logs that show when the auth request is occurring and what files worked before that occurred? Our team is still pretty confused and we seem to not be running into it internally.
Also, does your SVN client support 1.6 (it's not an older client)? Which client are you using?
I'll have a look
I wonder if the internal team is not having the trouble cus they all have url root access?? Is this the case by any change?'
I have the command line svn from collabnet 1.6.9 (updated whenever they do)
Also sometime use TortoiseSVN 18.104.22.16815(64)
Oh and the root url idea, thats just something pulled right out of left field but please don’t be surprised if it leads you nowhere. :-)
Cheers as always Matt
I was trying to update flex/sdk/trunk, and i got authorization request.
I run sniffer to find out what happened.
OPTIONS /svn/opensource HTTP/1.1
User-Agent: SVN/1.6.2 (r37639)/TortoiseSVN-22.214.171.12444 neon/0.28.4
Connection: TE, Keep-Alive
Authorization: Basic Og==
<?xml version="1.0" encoding="utf-8"?><D:options xmlns:D="DAV:"><D:activity-collection-set/></D:options>
HTTP/1.1 401 Authorization Required
Date: Thu, 04 Feb 2010 19:19:06 GMT
WWW-Authenticate: Basic realm="Opensource Subversion Repository"
Content-Type: text/html; charset=iso-8859-1
Expires: Thu, 04 Feb 2010 19:34:06 GMT
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<title>401 Authorization Required</title>
<p>This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
<address>Apache Server at opensource.adobe.com Port 80</address>
I think I may have finally figured out what's going on. Unfortunately, it's a huge nasty bug in Subversion. http://subversion.tigris.org/issues/show_bug.cgi?id=3242
Basically SVN for some reason goes up to the root to find out certain things like OPTIONS and PROPFIND and we don't allow access to the root. Glenn asked before whether our username/passwords have root access, and I think within Adobe they do.
We have to figure out if it's OK to allow the client to basically see what's going on at the root and then deny access further down, or what.
This is going to take some more time, but now we at least have a path...
great news. at least we all know what the problem is.
LOL, ok here's my easy answer. just give me root access, now of course i promise i wouldn't go checking out anything that suddenly started to show up in the projects directory. I'd just slide right past them and be a good boy. of course ;-)
well finding the problem is always 4/5th of the effort. so well done.