Forums | Users |
Search | Signup | Login

PROPFIND error

Subscribe to PROPFIND error 4 post(s), 3 voice(s)

 
Avatar Ken Smith 2 post(s)

After several months of successfully using unfuddle, I’ve suddenly stopped being able to add new files to my SVN repository. When I try to, say, add “test.txt” to the repository (using the latest version of Tortoise), I get the following results:

Command Commit
Adding K:\source\alanta\trunk\test.txt
Error Commit failed (details follow):
Error PROPFIND of
Error ‘/svn/alanta_alanta/!svn/wrk/15ed5a49-aec6-3643-95e3-ae9f2d609cdf/trunk/test.txt’:
Error 200 Ok (http://alanta.unfuddle.com)
Error PROPFIND of ‘/svn/alanta_alanta/trunk/test.txt’: 200 Ok (http://alanta.unfuddle.com)
Finished!

I can still check out, and I can still update existing files, but I can no longer add new ones. Any suggestions?

 
Avatar Joshua Frappier Administrator 378 post(s)

The problem you describe is almost always caused by a proxy or firewall which is prohibiting some or all of the DeltaV and WebDAV HTTP extensions required by Subversion. There are two ways to remedy this issue: 1) somehow bypass the offending proxy or firewall; or 2) use SSL to connect to the repository as most proxies do not filter SSL connections at all.

 
Avatar Ken Smith 2 post(s)

That must be what it was. I’d just upgraded my Linksys WRT 110 router’s firmware (from 1.0.02 to 1.0.07), and something about the new firmware doesn’t like the subversion flavor of the HTTP protocol. I tried turning off stateful packet inspection, but that didn’t do the trick. A question on the Linksys boards (http://forums.linksysbycisco.com/linksys/board/message?board.id=Wireless_Routers&thread.id=169355) hasn’t turned up any answers. But I backleveled my router to 1.0.02, and it’s working again. Oh well. Live and learn. (This isn’t the first time I’ve had trouble with a Linksys firmware upgrade. You’d think I’d have learned my lesson by now.)

 
Avatar mrbinky3000 1 post

Ken, I seem to be having the same exact problem and have the same router as you. What did you do to fix it? Did you revert back to 1.0.02?