On Thu, Dec 16, 2010 at 8:22 AM, Trou Macacq <mac...@gmail.com> wrote: > connected with HTTP_HOST env variable... And this env variable cannot > be changed either in CGI script using bash, or by using SetEnv > mod_rewreite directive.
You'll want to do one of two things here: (1) You'll want to investigate how I'm passing requests back to Fossil in my configuration and take good note of the relevant line in /etc/hosts combined with the host I use in my mod_proxy directives, along with how I'm binding Fossil to a particular loopback address. (2) You'll want to investigate how to use proxy_set_header to set the Host header in nginx. Using SetEnv with mod_rewrite, if memory serves, requires the use of the passthrough flag on that particular rule. I wouldn't advise doing this since it just muddles up your configuration with mod_rewrite rules, which can become cumbersome and hard to deal with very quickly. > About fossil server... on production (not ad hoc) this means using > inetd daemon. And I might say something stupid, but I'm almost sure it > not installed on my Ubuntu server 10.10 by default. And I trying to > keep everything as standard as possible. Is this itetd setup really > better than CGI. Where I can find a list of advantages and > disadvantages of this approach? I was hinting more at the analogue between my configuration and yours. If you want to mimic it, that's fine, but you're already on a good path here. My setup was more an illustration how I solved the same problem in my environment. > Many thanks in advance! Hope this helps, -- Nathaniel R. Reindl _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
