hugh williams wrote: [...] And yet another possibility, technically speaking. It is not secure in a general sense, and your sysadmins might not like it at all for good reasons. So this is not a recommendation, it is just to indicate what is possible technically. When Apache starts and reads its configuration file (apache2.conf or httpd.conf or whatever it is named in your case), this file can contain "Include" directives to include other files in the configuration.It would thus be a possibility to have such an "include" file, called from the main conf file, but residing somewhere else and having permissions such that you (and preferably you alone) can edit it. Then you would still have to ask your sysadmins to restart Apache when there is a change in the file, but you would not have to ask them for more.
For example, this file could contain a VirtualHost section, defining a particular Vhost that has the DNS name that you wish to tailor to your needs. There are some limitations as to what you could in there (*), but it would still give you wide customisation possibilities.
Again, not a real suggestion, and don't tell anyone that I even mentioned this.
(*) for example, you could not use a module that is not loaded in the main configuration section, or have this VHost listen on a port not opened in the main config.
--------------------------------------------------------------------- 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
|