The mod_wsgi documentation about hosting of static files wrongly refers to mod_python documentation.
|Reported by:||grahamd||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
In the page:
"""See the Apache/mod_python documentation for directions on serving static media"""
Reference to the mod_python documentation should not be done as how it is done for mod_python is different. When using mod_wsgi you do not need to use the hacks that have to be done when using mod_python because mod_wsgi interacts properly with other Apache directives such as the Alias directive such that it works with no hacks required. In other words, the 'Location/SetHandler None' hack used in mod_python isn't required.
As per example in:
and further described in:
all you need to do is use an Alias directive to map URL to location of static media files and then allow Apache to serve those media files. For example:
Alias /robots.txt /usr/local/wsgi/static/robots.txt Alias /favicon.ico /usr/local/wsgi/static/favicon.ico AliasMatch /([^/]*\.css) /usr/local/wsgi/static/styles/$1 Alias /media/ /usr/local/wsgi/static/media/ <Directory /usr/local/wsgi/static> Order deny,allow Allow from all </Directory> WSGIScriptAlias / /usr/local/wsgi/scripts/django.wsgi <Directory /usr/local/wsgi/scripts> Order allow,deny Allow from all </Directory>
You SHOULD NOT BE USING:
<Location "/media"> SetHandler None </Location> <LocationMatch "\.(jpg|gif|png)$"> SetHandler None </LocationMatch>
as given in the mod_python documentation and as currently referred to.