New answers tagged httpd.conf
Since you say that there's nothing in access.log, the request isn't arriving at your server. So, you need to fix the DNS for your domain, to point to your server. You can start by running host www.mydomain.com If the result doesn't show the IP address of your server, then you need to work through the domain registrar to fix that.
Another possible solution: <LocationMatch "/.+"> # ProxyPass directives </LocationMatch>
Redirect any requests for plain www.domain.com to www.domain.com/index.html and then add an proxy exclude before forwarding everything else to Tomcat: RewriteRule ^/$ /index.html ProxyPass /index.html ! ProxyPass / http://localhost:8080/ ProxyPassReverse / http://localhost:8080/
Not native with the ErrorLog Directive. What I would do is write a script that does the resolving for you and pipe the ErrorLog through that. In your apache config something like this: Errorlog "|/usr/local/bin/errorlog_resolver.pl" And then a sample Perl script: #!/usr/bin/perl -w # errorlog_resolver.pl # Give apache ErrorLog on STDIN, outputs them ...
With an AllowOverride None setting in the httpd.conf the .htaccess file is completely ignored. So you have to change that setting. When .htaccess files are allowed, apache will check each directory from the DocumentRoot down for the existance of a .htaccess file AND will apply the settings there, before desccending down to the next directory and the ...
Does that mean that RewriteEngineOn can be used multiple times within httpd.conf? Yes, that's fine. I'm assuming that it can be but it must be placed within directory blocks. No, it's valid in any configuration context, and will inherit down to other contexts - so if you have it enabled at the <VirtualHost>, you don't need it within ...
AFAIK Apache processes its configuration file in order. Includes are processed at the point and the order they're referenced in, effectively creating a single configuration. To have changes there take effect apache needs to be reloaded/restarted. That can fail so is not something users should be allowed to do. The typical way to allow user to somewhat ...
try mod_macro Here is an example: ## Define a VHost Macro for repetitive configurations <Macro VHost $host $port $dir> Listen $port <VirtualHost *:$port> ServerName $host DocumentRoot $dir # Public document root <Directory $dir> Require all granted </Directory> # limit access to intranet subdir. ...
I'm thinking maybe you could create a config file with your variable declarations, include it in the httpd.conf file, and then run a cron job to change the server name to whatever is currently the server name using sed. Example cron job: set servername = hostname sed -i -e 's/(?-s)define servername .+/define servername $servername/g' ...
Top 50 recent answers are included