Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change 
notification.

The following page has been changed by slive:
http://wiki.apache.org/httpd/Recipes/Different_UserIDs_Using_Reverse_Proxy

The comment on the change is:
Clarify UseCanonicalName and other directives that might need changes

------------------------------------------------------------------------------
  
  If you use unprivileged ports for the back-end hosts (for example, replacing 
81 and 82 above with 8001 and 8002) then you may choose to start these hosts 
directly under the less-privileged userids (host1user and host2user) in place 
of root. This will allow you to give complete control of these back-end servers 
to host1user and host2user. These users could then edit httpd.conf and manage 
log files and server restarts without needing root privileges. You may also 
choose to run the back-end hosts in a chroot environment, in a FreeBSD jail, or 
under other restricted permissions (using SELinux, for example).
  
+ When starting httpd under a less-privileged userid, you'll need to adjust 
certain directives such as {{{PIDFile}}} and {{{CustomLog}}} to point to 
locations writable by the less-privileged user.
+ 
  == Alternative Proxy Configuration ==
  
  If back-end hosts might be added and removed frequently, it could be helpful 
to be able to do this without modifying the configuration of the front-end 
server. Here is an example config that allows back-end hosts to be added and 
deleted by editing a simple text database:
@@ -100, +102 @@

  www.bar.com 127.0.0.1:8001
  }}}
  
- Because the {{{ProxyPreserveHost}}} directive is used in place of 
{{{ProxyPassReverse}}} in this configuration, you need to ensure that the 
back-end hosts use the following (which is the default):
+ Because the {{{ProxyPreserveHost}}} directive is used in place of 
{{{ProxyPassReverse}}} in this configuration, you need to ensure that the 
back-end hosts use the following config in order to get the correct hostname 
and port on server-generated redirects:
  {{{
  UseCanonicalName Off
  }}}

Reply via email to