| 2010-03-05 11:04:13 |
Szilveszter Farkas |
description |
Currently you need to specify most of the directives in both Location blocks, if you have a separate action-path set. |
Currently you need to specify most of the directives in both Location blocks, if you have a separate action-path set.
Example:
<Location "/">
PythonAccessHandler apache_openid::protect
PythonOption action-path "/openid/"
PythonOption handler "openidteams"
PythonOption store-type file
PythonOption store-directory /tmp/apache-openid/
PythonOption allowed-op-list-url "file:///etc/apache2/openid/allowed-ops.txt"
PythonOption authorized-teams-list-url "file:///etc/apache2/openid/teams.txt"
</Location>
<Location "/openid/">
SetHandler mod_python
PythonHandler apache_openid::protect
PythonOption action-path "/openid/"
PythonOption handler "openidteams"
PythonOption store-type file
PythonOption store-directory /tmp/apache-openid/
PythonOption allowed-op-list-url "file:///etc/apache2/security/allowed-ops.txt"
PythonOption authorized-teams-list-url "file:///etc/apache2/openid/teams.txt"
</Location>
A possible solution: store the config in a separate file (e.g. INI-style), and point only to that file from the Location blocks.
We also need to look into cases where each Location allows different teams. |
|
