I've got SVN::Web 0.52 running on Apache 2.2.4/Subversion 1.4.3/Apache2::RequestRec (mod_perl) 2.000003 on a RHEL 4.3 box. Without svnweb, the svn services are fine (but are boring to view). Configuring svnweb has been a challenge. If I try to look at the contents of project 'abc' with a web browser I get this error (url for this at my site is https://svn/svnweb/abc):

However when I force a reload on the page, it comes up fine.

Next problem: Links deeper down are messed up. If I follow abc's trunk and try to examine some source code there, the links generated by svnweb look like this:

The %2F should be a forward slash, in otherwords, the generated url should be

If I manually replace the %2F with / and reload, it shows the desired page just fine. Manually doing that change gets old fast though!

Anyone have clues to resolving these problems?

For #1 I added the trailing slash for the original top level url and that fixed the problem. But auto generated url's deeper down appear without the slash and adding the slash there doesn't fix it; only a reload will. I appreciate your offer to look at my httpd.conf; I'll try to identify the relevant sections and send those. #2: I issued this command in the template/trac directory:

and it looks like it inserted the slash in the right places. Here's an example from one of the files:

Now when I browse the repository I see the extra slash--but the %2F is there too: https://svn/svnweb/rexdb/browse/rexdb/browse/%2Ftrunk/src also it introduced a new problem, now there are two slashes after "browse" in a higher level url: https://svn/svnweb/rexdb/browse//rexdb/ and much of the nice formatting is gone, I see vanilla html as I do without svnweb. Probably my perl edit command was overly aggressive.

There is another solution if you use Apache >= 2.0.46. Add the following directive in the apache conf:

This will allow %2F in urls and it solved the problems for me.