On Tue, May 27, 2014 at 11:31 PM, Warren Young <war...@etr-usa.com> wrote: > On 5/27/2014 17:10, Joe Prostko wrote: >> >> On May 27, 2014 6:58 PM, "Warren Young" <war...@etr-usa.com >> <mailto:war...@etr-usa.com>> wrote: >> >> > Incidentally, I'm bothering with nginx proxying because the SCGI >> method seems to have broken in 1.28. It was working fine on my site >> with 1.27 from the Ubuntu repository until I upgraded to 1.28 by >> building from source. (I wanted the /tree feature.) >> >> This should work in trunk or when 1.29 comes out, as Richard fixed it >> post 1.28. > > > Confirmed. I'm back on SCGI now. Thanks!
No problem! I reported it some time back, and Richard committed the fix. > 1. You don't need to do regex matching on the URL here. This does the same > thing more efficiently and more clearly: > > location /demo_project/ { > > nginx does prefix matching by default. Using regex matching (~) just to pin > the match to the start of the path with ^ adds nothing. I always write this as: location ~ ^/demo_project { myself. That way, it's a case-sensitive search where I don't have to worry about the trailing slash, and it stops searching once it finds /demo_project. I could be mistaken though, but I thought the way you suggested wouldn't be as flexible. I guess I'd have to test it to be sure, as anything resembling regex is kind of like black magic to me. ;) - joe _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users