When I’m trying to connect to my SVN server at http://svn.ourdomain.com/architecture/ (mind the trailing slash), VP cuts off the trailing slash and sends the request (WebDav PROPFIND, not really important) to http://svn.ourdomain.com/architecture instead (without trailing slash). By default, my SVN server then returns a 301 to send the client to /architecture/, since that is the correct directory.
VP seems not to be able to properly follow the 301 redirect and I can’t find a way to prevent it from cutting off the trailing slash. Is there a way to fix that behaviour?
Thanks in advance
Maarten Manders
Edit:
I also tried other SVN executables, same result
I got my information by analysing the communication with Wireshark (Ethereal)
Thank you for your post. I have forwarded your problem to our engineers to follow up. Could you post the vp.log file here? You can find it inside ${vp-suite-install-dir}/bin
Thanks for the quick response! Here’s what the vp.log says:
[Tue Jun 05 18:33:00 CEST 2007] [message] [Tue Jun 05 18:33:00 CEST 2007]: Start Visual Paradigm for UML Standard Edition [VP-UML SE]: 6.0 (sp2_20070526)
[Tue Jun 05 18:35:17 CEST 2007] [error] ExecuteOutput err svn: PROPFIND request failed on '/architecture'
[Tue Jun 05 18:35:17 CEST 2007] [error] ExecuteOutput err svn: PROPFIND of '/architecture': 301 Moved Permanently (http://svn.tilllate.com)
[Tue Jun 05 18:35:17 CEST 2007] [warning] login svn fail , errMsg : null
Thanks for your reply. Will talk to our engineers about the problem. It seems that it is really due to the trailing slash. We still need to check in more detail.
Might very well be. I just followed a TortoiseSVN session, which cuts off the trailing slash as well. Allthough your suggested FAQ article doesn’t apply, the error seems to be on our apache server. Trying to fix it and report.
We’ve analyzed this case and found out that it’s got to be a misconfiguration of our server. For browsers, it should send a 301 when the trailing slash is missing for directories, for svn clients it shouldn’t. Unfortunately, our Apache does it anyway.
Anyway, this isn’t a bug in VP, sorry for the bogus report.