> On 8 Jan 2017, at 3:58 AM, Cristian P <[email protected]> wrote:
>
> Thank you so much that work perfectly.
> Is there a proper way to create list of Aliases that should bypass wsgi
> besides multiple of these statements.
>
> The second way sounds interesting, how would the wsgi script be able to pick
> up the path_info?
URLs handled by mod_userdir are a special case. The default order has to be the
way it is else you wouldn't be able to use WSGI applications setup using
AddHandler inside of a users personal directory.
For any other aliases, just use the Alias directive as Alias will always
override WSGIScriptAlias.
Thus if you need to have static files at a sub URL, or a directory with PHP
files in it, you would have:
Alias /suburl /some/path/to/static/files
WSGIScriptAlias / /some/path/to/wsgi.py
Note that order actually doesn't matter here as Alias truly always overrides
WSGIScriptAlias, not done by order in file.
Order is important in a case like:
WSGIScriptAlias /suburl /some/other/path/to/wsgi.py
WSGIScriptAlias / /some/path/to/wsgi.py
where the deepest sub URLs should be first as they are matched in order within
set of WSGIScriptAlias directives.
Same occurs for Alias, so if have more than one of those, list in order so that
most specific is first.
Graham
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
