Put location tag in apache2 configuration file

apache-2.2configuration

I want to put expiration setting similar to mentioned here. Apache caching with mod_headers mod_expires

However I am not sure where should I put that code. I am running apach2 on ubuntu and I have 4 vhost in my apache. A vhost config is something similar to this one

<VirtualHost xx.xx.xx.xx:80>
ServerName xxxxxx
ServerAlias xxxxxxxxxx
DocumentRoot /home/xxxx/current/public
<Directory "/home/xxx/current/public">
        Options FollowSymLinks
        AllowOverride None
        Order allow,deny
        Allow from all
</Directory>
</VirtualHost>

My gut feeling is that I should put stuff after the end of directory. That would be after this tag . Is that the right place to put the expiration code.

And I am also assuming that I would be repeating the same code for all 4 vhosts. They all need same configuration.

Best Answer

You can put it anywhere inside <VirtualHost>. So after <Directory>…</Directory> is fine, as is before it, or between ServerName and ServerAlias, etc.

You can probably put it outside the vhost as well, in which case it'll apply to all vhosts (but I'm not completely sure on this).

Related Solutions

Apache deny directive not working

That should work. I just verified your code on my server to make sure I wasn't crazy. Are you sure you don't have a definition before this one that is taking precedence?

Create a test file in the folder on your server. Something like test.txt. You may find that you don't see it when you load that url in your browser. If that's the case then your definition above is getting skipped.

Apache configuration problem with and

You should be able to do this with multiple <Directory> blocks. Here is a link to the applicable apache documentation:

http://httpd.apache.org/docs/2.2/sections.html

I think the key items for your case are:

What to use When

Choosing between filesystem containers and webspace containers is actually quite easy. When applying directives to objects that reside in the filesystem always use <Directory> or <Files>. When applying directives to objects that do not reside in the filesystem (such as a webpage generated from a database), use <Location>.

It is important to never use <Location> when trying to restrict access to objects in the filesystem. This is because many different webspace locations (URLs) could map to the same filesystem location, allowing your restrictions to be circumvented.

Also http://httpd.apache.org/docs/2.2/sections.html#mergin - specifically:

Apart from <Directory>, each group is processed in the order that they appear in the configuration files. <Directory> (group 1 above) is processed in the order shortest directory component to longest. So for example, <Directory /var/web/dir> will be processed before <Directory /var/web/dir/subdir>. If multiple <Directory> sections apply to the same directory they are processed in the configuration file order. Configurations included via the Include directive will be treated as if they were inside the including file at the location of the Include directive.

I think this will work:

<Directory "/srv/www/example.com">
    AllowOverride All
    Options FollowSymlinks -Indexes
    Order deny,allow
    Allow from 127.0.0.0/8 1.2.3.4 5.6.7.8
    # our IP
    Allow from 4.3.2.1
    # PayPal IPN
    Allow from 216.113.191.33
#    Deny from all

    AuthType Basic
    AuthName "Restricted Files"
    AuthUserFile /srv/www/htdocs/.htpasswd
    Require valid-user
    Satisfy Any
</Directory>
<Directory "/srv/www/example.com/url/to/config.xml">
    Order allow,deny
    Allow from all
</Directory>

Best Answer

Related Solutions

Apache deny directive not working

Apache configuration problem with and

Related Topic