Krist, > What happens if you try to request this directly in a browser, eg. you try to request: https://svn.mydomain.com/htdocs/svindex.xsl Going to that url results in the error message "Could not open the requested SVN filesystem" being displayed, which sounds like Subversion / DAV is still trying to process this url instead of letting Apache handle it. The message in the error log file is very similar ... [Mon Oct 06 11:13:35 2008] [error] [client 192.168.1.51] (20014)Internal error: Can't open file 'F:\\Repositories\\svnindex.xsl\\format': The system cannot find the path specified. [Mon Oct 06 11:13:35 2008] [error] [client 192.168.1.51] Could not fetch resource information. [500, #0] [Mon Oct 06 11:13:35 2008] [error] [client 192.168.1.51] Could not open the requested SVN filesystem [500, #720003] [Mon Oct 06 11:13:35 2008] [error] [client 192.168.1.51] Could not open the requested SVN filesystem [500, #720003] I believe this is the root of the issues in that SVN / DAV is handling all requests. Thanks -- Jeff -----Original Message----- From: Krist van Besien [mailto:krist.vanbesien@xxxxxxxxx] Sent: Monday, October 06, 2008 11:05 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: Apache Conf. Issue - SVN On Mon, Oct 6, 2008 at 4:50 PM, Jeff Chastain <lists@xxxxxxxxxxxx> wrote: > But, yeah, if I had > thought through it I would have realized that you are not supposed to be > able to do this and can't with IIS at least. You can't do this with Apache nor with IIS ,and it has nothing to do with a limitation of the software. The problem is in the SSL protocol.. > For the SVN virtual host, the documentRoot parameter is set to "C:/Program > Files/VisualSVN Server". Within the "/" location block, the SVNIndexXSLT > parameter is set to "/htdocs/svnindex.xsl", thus the full file system path > to the XSLT file is "C:/Program Files/VisualSVN Server/htdocs/svnindex.xsl" > which is correct and valid. What happens If you try to request this directly in a browser, eg. you try to request: https://svn.mydomain.com/htdocs/svindex.xsl It could be that the sever just won't allow you to get the file. Also check what the error log says. When you get an error code usually there will be something in the errorlog indicating what might be the problem. Krist -- krist.vanbesien@xxxxxxxxx krist@xxxxxxxxxxxxx Bremgarten b. Bern, Switzerland -- A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? A: Top-posting. Q: What's the biggest scourge on plain text email discussions? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|