Thanks for the suggestions. In the end I found that unless the site root was handled by mono (currently only /cashless/ is handled), the // would continue to cause problems. However, this change brought its own problems - php pages stopped being served correctly and mono started to redirect subfolder pages back to the root. In the end, the solution which allowed me to continue serving php pages correctly and avoid changes to my .net app was just to add: > <LocationMatch //> > Order allow,deny > Deny from all > </LocationMatch> > to my apache2.conf. Probably not the most elegant solution in the world, but given that the site is internal and not customer facing I think that it is adequate. -- View this message in context: http://www.nabble.com/Code-Pages-Downloadable%21-tf4747449.html#a13622720 Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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
|