Changes between Version 1 and Version 2 of TracModWSGI


Ignore:
Timestamp:
Oct 22, 2021, 8:34:04 PM (7 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracModWSGI

    v1 v2  
    1 = Trac and mod_wsgi =
    2 
    3 
    4 [http://code.google.com/p/modwsgi/ mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performance.
     1= Trac and mod_wsgi
     2
     3[https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performance.
    54
    65[[PageOutline(2-3,Overview,inline)]]
     
    87== The `trac.wsgi` script
    98
    10 Trac can be run on top of mod_wsgi with the help of the following application script, which is just a Python file, though usually saved with a `.wsgi` extension).
     9Trac can be run on top of mod_wsgi with the help of an application script, which is a Python file saved with a `.wsgi` extension.
     10
     11A robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths, see TracInstall#cgi-bin. The script should be sufficient for most installations and users not wanting more information can proceed to [#Mappingrequeststothescript configuring Apache].
     12
     13If you are using Trac with multiple projects, you can specify their common parent directory in `trac.wsgi`:
     14{{{#!python
     15def application(environ, start_request):
     16    # Add this when you have multiple projects
     17    environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects')
     18    ..
     19}}}
     20
     21Directories residing in `trac.env_parent_dir` that are not environment directories will display an error message on the [TracInterfaceCustomization#ProjectList project index page]. The directories can be excluded by listing them in a `.tracignore` file residing in `trac.env_parent_dir`. Unix [https://docs.python.org/2/library/fnmatch.html shell-style wildcard patterns] can be used in the newline separated list of directories.
    1122
    1223=== A very basic script
     24
    1325In its simplest form, the script could be:
    1426
     
    2335}}}
    2436
    25 The `TRAC_ENV` variable should naturally be the directory for your Trac environment (if you have several Trac environments in a directory, you can also use `TRAC_ENV_PARENT_DIR` instead), while the `PYTHON_EGG_CACHE` should be a directory where Python can temporarily extract Python eggs.
     37The `TRAC_ENV` variable should naturally be the directory for your Trac environment, and the `PYTHON_EGG_CACHE` should be a directory where Python can temporarily extract Python eggs. If you have several Trac environments in a directory, you can also use `TRAC_ENV_PARENT_DIR` instead of `TRAC_ENV`.
    2638
    2739On Windows:
     
    3042os.environ['PYTHON_EGG_CACHE'] = r'C:\Users\Administrator\AppData\Roaming\Python-Eggs'
    3143}}}
    32  - If run under a Window service, you should create a directory for Python Egg cache.
     44 - If run under a Window service, you should create a directory for Python Egg cache:
    3345{{{#!python
    3446os.environ['PYTHON_EGG_CACHE'] = r'C:\Trac-Python-Eggs'
     
    3749=== A more elaborate script
    3850
    39 If you're using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment.
     51If you are using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment.
    4052
    4153To solve this problem, use the following `.wsgi` file instead:
     
    4759import trac.web.main
    4860def application(environ, start_response):
    49   environ['trac.env_path'] = '/usr/local/trac/mysite' 
     61  environ['trac.env_path'] = '/usr/local/trac/mysite'
    5062  return trac.web.main.dispatch_request(environ, start_response)
    5163}}}
    5264
    53 For clarity, you should give this file a `.wsgi` extension. You should probably put the file in its own directory, since you will expose it to Apache. 
    54 
    55 If you have installed Trac and eggs in a path different from the standard one you should add that path by adding the following code at the top of the wsgi script:
     65For clarity, you should give this file a `.wsgi` extension. You should probably put the file in its own directory, since you will expose it to Apache.
     66
     67If you have installed Trac and Python eggs in a path different from the standard one, you should add that path by adding the following code at the top of the wsgi script:
    5668
    5769{{{#!python
     
    6274Change it according to the path you installed the Trac libs at.
    6375
    64 === Recommended `trac.wsgi` script
    65 
    66 A somewhat robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths (see TracInstall#cgi-bin).
    67 
    68 
    6976== Mapping requests to the script
    7077
    71 After you've done preparing your .wsgi script, add the following to your Apache configuration file (`httpd.conf` for example).
    72 
    73 {{{
     78After preparing your .wsgi script, add the following to your Apache configuration file, typically `httpd.conf`:
     79
     80{{{#!apache
    7481WSGIScriptAlias /trac /usr/local/trac/mysite/apache/mysite.wsgi
    7582
    7683<Directory /usr/local/trac/mysite/apache>
    7784    WSGIApplicationGroup %{GLOBAL}
    78     Order deny,allow
    79     Allow from all
     85    # For Apache 2.2
     86    <IfModule !mod_authz_core.c>
     87        Order deny,allow
     88        Allow from all
     89    </IfModule>
     90    # For Apache 2.4
     91    <IfModule mod_authz_core.c>
     92        Require all granted
     93    </IfModule>
    8094</Directory>
    8195}}}
     
    8599If you followed the directions [TracInstall#cgi-bin Generating the Trac cgi-bin directory], your Apache configuration file should look like following:
    86100
    87 {{{
     101{{{#!apache
    88102WSGIScriptAlias /trac /usr/share/trac/cgi-bin/trac.wsgi
    89103
    90104<Directory /usr/share/trac/cgi-bin>
    91105    WSGIApplicationGroup %{GLOBAL}
    92     Order deny,allow
    93     Allow from all
     106    # For Apache 2.2
     107    <IfModule !mod_authz_core.c>
     108        Order deny,allow
     109        Allow from all
     110    </IfModule>
     111    # For Apache 2.4
     112    <IfModule mod_authz_core.c>
     113        Require all granted
     114    </IfModule>
    94115</Directory>
    95116}}}
    96117
    97 In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the `WSGIApplicationGroup` directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi; this is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other sub-interpreters and may cause requests to hang or cause Apache to crash as a result. After adding this configuration, restart Apache, and then it should work.
    98 
    99 To test the setup of Apache, mod_wsgi and Python itself (ie. without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script):
     118In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the `WSGIApplicationGroup` directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi. This is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other sub-interpreters and may cause requests to hang or cause Apache to crash. After adding this configuration, restart Apache, and then it should work.
     119
     120To test the setup of Apache, mod_wsgi and Python itself (ie without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script):
    100121
    101122{{{#!python
     
    105126}}}
    106127
    107 For more information about using the mod_wsgi specific directives, see the [http://code.google.com/p/modwsgi/wiki/ mod_wsgi's wiki] and more specifically the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac IntegrationWithTrac] page.
    108 
     128For more information about using the mod_wsgi specific directives, see the [https://code.google.com/archive/p/modwsgi/wikis mod_wsgi's wiki] and more specifically the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki IntegrationWithTrac] page.
    109129
    110130== Configuring Authentication
    111131
    112 We describe in the the following sections different methods for setting up authentication.
    113 
    114 See also [http://httpd.apache.org/docs/2.2/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
    115 
    116 === Using Basic Authentication ===
    117 
    118 The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program to create the password file:
    119 {{{
     132The following sections describe different methods for setting up authentication. See also [https://httpd.apache.org/docs/2.4/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
     133
     134=== Using Basic Authentication
     135
     136The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program as follows:
     137{{{#!sh
    120138$ htpasswd -c /somewhere/trac.htpasswd admin
    121139New password: <type password>
     
    124142}}}
    125143
    126 After the first user, you dont need the "-c" option anymore:
    127 {{{
     144After the first user, you don't need the "-c" option anymore:
     145{{{#!sh
    128146$ htpasswd /somewhere/trac.htpasswd john
    129147New password: <type password>
     
    132150}}}
    133151
    134   ''See the man page for `htpasswd` for full documentation.''
     152See the man page for `htpasswd` for full documentation.
    135153
    136154After you've created the users, you can set their permissions using TracPermissions.
    137155
    138 Now, you'll need to enable authentication against the password file in the Apache configuration:
    139 {{{
     156Now, you need to enable authentication against the password file in the Apache configuration:
     157{{{#!apache
    140158<Location "/trac/login">
    141159  AuthType Basic
     
    146164}}}
    147165
    148 If you're hosting multiple projects you can use the same password file for all of them:
    149 {{{
     166If you are hosting multiple projects, you can use the same password file for all of them:
     167{{{#!apache
    150168<LocationMatch "/trac/[^/]+/login">
    151169  AuthType Basic
     
    155173</LocationMatch>
    156174}}}
    157 Note that neither a file nor a directory named 'login' needs to exist.[[BR]]
    158 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html mod_auth_basic] documentation.
    159 
    160 === Using Digest Authentication ===
    161 
    162 For better security, it is recommended that you either enable SSL or at least use the “digest” authentication scheme instead of “Basic”.
    163 
    164 You'll have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:
    165 {{{
    166 # htdigest -c /somewhere/trac.htpasswd trac admin
     175
     176Note that neither a file nor a directory named 'login' needs to exist. See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_basic] documentation.
     177
     178=== Using Digest Authentication
     179
     180For better security, it is recommended that you either enable SSL or at least use the "digest" authentication scheme instead of "Basic".
     181
     182You have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:
     183{{{#!sh
     184$ htdigest -c /somewhere/trac.htpasswd trac admin
    167185}}}
    168186
    169187The "trac" parameter above is the "realm", and will have to be reused in the Apache configuration in the !AuthName directive:
    170188
    171 {{{
     189{{{#!apache
    172190<Location "/trac/login">
    173 
    174     AuthType Digest
    175     AuthName "trac"
    176     AuthDigestDomain /trac
    177     AuthUserFile /somewhere/trac.htpasswd
    178     Require valid-user
     191  AuthType Digest
     192  AuthName "trac"
     193  AuthDigestDomain /trac
     194  AuthUserFile /somewhere/trac.htpasswd
     195  Require valid-user
    179196</Location>
    180197}}}
     
    182199For multiple environments, you can use the same `LocationMatch` as described with the previous method.
    183200
    184 '''Note: `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity. '''
     201'''Note''': `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity.
    185202
    186203Don't forget to activate the mod_auth_digest. For example, on a Debian 4.0r1 (etch) system:
    187 {{{
    188     LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
    189 }}}
    190 
    191 
    192 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html mod_auth_digest] documentation.
    193 
    194 === Using LDAP Authentication
    195 
    196 Configuration for [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap] authentication in Apache is a bit tricky (httpd 2.2.x and OpenLDAP: slapd 2.3.19)
    197 
    198 1. You need to load the following modules in Apache httpd.conf
    199 {{{
    200 LoadModule ldap_module modules/mod_ldap.so
    201 LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    202 }}}
    203 
    204 2. Your httpd.conf also needs to look something like:
    205 
    206 {{{
     204{{{#!apache
     205  LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
     206}}}
     207
     208See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_digest] documentation.
     209
     210=== Using LDAP Authentication
     211
     212Configuration for [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2+ and OpenLDAP: slapd 2.3.19).
     213
     2141. You need to load the following modules in Apache httpd.conf:
     215{{{#!apache
     216  LoadModule ldap_module modules/mod_ldap.so
     217  LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
     218}}}
     2191. Your httpd.conf also needs to look something like:
     220{{{#!apache
    207221<Location /trac/>
    208222  # (if you're using it, mod_python specific settings go here)
     
    218232</Location>
    219233}}}
    220 
    221 
    222 3. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory:
    223 
    224 
    225 Use the following as your LDAP URL:
    226 {{{
    227     AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
    228 }}}
    229 
    230 You will also need to provide an account for Apache to use when checking
    231 credentials. As this password will be listed in plaintext in the
    232 config, you should be sure to use an account specifically for this task:
    233 {{{
    234     AuthLDAPBindDN ldap-auth-user@example.com
    235     AuthLDAPBindPassword "password"
    236 }}}
    237 
    238 The whole section looks like:
    239 {{{
     2341. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory. Use the following as your LDAP URL:
     235{{{#!apache
     236  AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
     237}}}
     238 You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plain text in the configuration, you need to use an account specifically for this task:
     239{{{#!apache
     240  AuthLDAPBindDN ldap-auth-user@example.com
     241  AuthLDAPBindPassword "password"
     242}}}
     243 The whole section looks like:
     244{{{#!apache
    240245<Location /trac/>
    241246  # (if you're using it, mod_python specific settings go here)
     
    251256  authzldapauthoritative Off
    252257  # require valid-user
    253   require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
     258  Require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
    254259</Location>
    255260}}}
    256261
    257 Note 1: This is the case where the LDAP search will get around the multiple OUs, conecting to Global Catalog Server portion of AD (Notice the port is 3268, not the normal LDAP 389). The GCS is basically a "flattened" tree which allows searching for a user without knowing to which OU they belong.
    258 
    259 Note 2: You can also require the user be a member of a certain LDAP group, instead of
    260 just having a valid login:
    261 {{{
    262     Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com
     262Note 1: This is the case where the LDAP search will get around the multiple OUs, conecting to the Global Catalog Server portion of AD. Note the port is 3268, not the normal LDAP 389. The GCS is basically a "flattened" tree which allows searching for a user without knowing to which OU they belong.
     263
     264Note 2: You can also require the user be a member of a certain LDAP group, instead of just having a valid login:
     265{{{#!apache
     266  Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com
    263267}}}
    264268
    265269See also:
    266   - [http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap
    267    
    268  - [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
    269  - [http://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
     270 - [https://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.
     271 - [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
     272 - [https://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
    270273
    271274=== Using SSPI Authentication
    272275
    273 If you are using Apache on Windows, you can use mod_auth_sspi to provide
    274 single-sign-on. Download the module from the !SourceForge [http://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the
    275 following to your !VirtualHost:
    276 {{{
    277     <Location /trac/login>
    278         AuthType SSPI
    279         AuthName "Trac Login"
    280         SSPIAuth On
    281         SSPIAuthoritative On
    282         SSPIDomain MyLocalDomain
    283         SSPIOfferBasic On
    284         SSPIOmitDomain Off
    285         SSPIBasicPreferred On
    286         Require valid-user
    287     </Location>
    288 }}}
    289 
    290 Using the above, usernames in Trac will be of the form `DOMAIN\username`, so
    291 you may have to re-add permissions and such. If you do not want the domain to
    292 be part of the username, set `SSPIOmitDomain On` instead.
     276If you are using Apache on Windows, you can use mod_auth_sspi to provide single-sign-on. Download the module from the !SourceForge [https://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the following to your !VirtualHost:
     277{{{#!apache
     278<Location /trac/login>
     279  AuthType SSPI
     280  AuthName "Trac Login"
     281  SSPIAuth On
     282  SSPIAuthoritative On
     283  SSPIDomain MyLocalDomain
     284  SSPIOfferBasic On
     285  SSPIOmitDomain Off
     286  SSPIBasicPreferred On
     287  Require valid-user
     288</Location>
     289}}}
     290
     291Using the above, usernames in Trac will be of the form `DOMAIN\username`, so you may have to re-add permissions and such. If you do not want the domain to be part of the username, set `SSPIOmitDomain On` instead.
    293292
    294293Some common problems with SSPI authentication: [trac:#1055], [trac:#1168] and [trac:#3338].
     
    296295See also [trac:TracOnWindows/Advanced].
    297296
    298 === Using Apache authentication with the Account Manager plugin's Login form ===
    299 
    300 To begin with, see the basic instructions for using the Account Manager plugin's [http://trac-hacks.org/wiki/AccountManagerPlugin/Modules#LoginModule Login module] and its [http://trac-hacks.org/wiki/AccountManagerPlugin/AuthStores#HttpAuthStore HttpAuthStore authentication module].
    301 
    302 '''Note:''' If is difficult to get !HttpAuthStore to work with WSGI when using any Account Manager version prior to acct_mgr-0.4. Upgrading is recommended.
    303 
    304 Here is an example (from the !HttpAuthStore link) using acct_mgr-0.4 for hosting a single project:
    305 {{{
    306 [components]
    307 ; be sure to enable the component
    308 acct_mgr.http.HttpAuthStore = enabled
    309 
    310 [account-manager]
    311 ; configure the plugin to use a page that is secured with http authentication
    312 authentication_url = /authFile
    313 password_store = HttpAuthStore
    314 }}}
    315 This will generally be matched with an Apache config like:
    316 {{{
    317 <Location /authFile>
    318    …HTTP authentication configuration…
    319    Require valid-user
    320 </Location>
    321 }}}
    322 Note that '''authFile''' need not exist (unless you are using Account Manager older than 0.4). See the !HttpAuthStore link above for examples where multiple Trac projects are hosted on a server.
     297=== Using CA !SiteMinder Authentication
     298
     299Setup CA !SiteMinder to protect your Trac login URL, for example `/trac/login`. Also, make sure the policy is set to include the HTTP_REMOTE_USER variable. If your site allows it, you can set this in `LocalConfig.conf`:
     300{{{#!apache
     301RemoteUserVar="WHATEVER_IT_SHOULD_BE"
     302SetRemoteUser="YES"
     303}}}
     304
     305The specific variable is site-dependent. Ask your site administrator. If your site does not allow the use of `LocalConfig.conf` for security reasons, have your site administrator set the policy on the server to set REMOTE_USER.
     306
     307Also add a !LogOffUri parameter to the agent configuration, for example `/trac/logout`.
     308
     309Then modify the trac.wsgi script generated using `trac-admin <env> deploy <dir>` to add the following lines, which extract the `HTTP_REMOTE_USER` variable and set it to `REMOTE_USER`:
     310
     311{{{#!python
     312def application(environ, start_request):
     313    # Set authenticated username on CA SiteMinder to REMOTE_USER variable
     314    # strip() is used to remove any spaces on the end of the string
     315    if 'HTTP_SM_USER' in environ:
     316        environ['REMOTE_USER'] = environ['HTTP_REMOTE_USER'].strip()
     317    ...
     318}}}
     319
     320You do not need any Apache "Location" directives.
    323321
    324322=== Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host
    325323
    326 Per the mod_wsgi documentation linked to above, here is an example Apache configuration that a) serves the Trac instance from a virtualhost subdomain and b) uses Apache basic authentication for Trac authentication.
    327 
    328 
    329 If you want your Trac to be served from e.g. !http://trac.my-proj.my-site.org, then from the folder e.g. `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first:
     324Per the mod_wsgi documentation linked to above, here is an example Apache configuration that:
     325 - serves the Trac instance from a virtualhost subdomain
     326 - uses Apache basic authentication for Trac authentication.
     327
     328If you want your Trac to be served from eg !http://trac.my-proj.my-site.org, then from the folder eg `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first:
    330329
    331330Create the htpasswd file:
    332 {{{
     331{{{#!sh
    333332cd /home/trac-for-my-proj/the-env
    334333htpasswd -c htpasswd firstuser
     
    336335htpasswd htpasswd seconduser
    337336}}}
    338 (keep the file above your document root for security reasons)
    339 
    340 Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` with the following contents:
    341 
    342 {{{
     337
     338Keep the file above your document root for security reasons.
     339
     340Create this file for example `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` on Ubuntu with the following content:
     341
     342{{{#!apache
    343343<Directory /home/trac-for-my-proj/the-deploy/cgi-bin/trac.wsgi>
    344344  WSGIApplicationGroup %{GLOBAL}
     
    361361}}}
    362362
    363 Note: for subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
    364 
     363For subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
    365364
    366365== Troubleshooting
     
    368367=== Use a recent version
    369368
    370 Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [http://code.google.com/p/modwsgi/issues/detail?id=100 #100] and [http://code.google.com/p/modwsgi/issues/detail?id=132 #132].
    371 
    372 ''Note: using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [http://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks''
    373 
    374 If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you'll even need version 0.3.4 or greater (see [trac:#10675] for details).
    375 
    376 === Getting Trac to work nicely with SSPI and 'Require Group' ===
    377 If like me you've set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your apache configuration, then the SSPIOmitDomain option is probably not working.  If its not working your usernames in trac are probably looking like 'DOMAIN\user' rather than 'user'.
    378 
    379 This WSGI script 'fixes' things, hope it helps:
     369Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem, attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [https://code.google.com/archive/p/modwsgi/issues/100 #100] and [https://code.google.com/archive/p/modwsgi/issues/132 #132].
     370
     371'''Note''': using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [https://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks
     372
     373If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you will need version 3.4 or greater. See [trac:#10675] for details.
     374
     375=== Getting Trac to work nicely with SSPI and 'Require Group'
     376
     377If you have set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your Apache configuration, then the SSPIOmitDomain option is probably not working. If it is not working, your usernames in Trac probably look like 'DOMAIN\user' rather than 'user'.
     378
     379This WSGI script fixes that:
    380380{{{#!python
    381381import os
     
    391391}}}
    392392
    393 
    394 === Trac with PostgreSQL ===
    395 
    396 When using the mod_wsgi adapter with multiple Trac instances and PostgreSQL (or MySQL?) as a database back-end, the server ''may'' create a lot of open database connections and thus PostgreSQL processes.
    397 
    398 A somewhat brutal workaround is to disabled connection pooling in Trac. This is done by setting `poolable = False` in `trac.db.postgres_backend` on the `PostgreSQLConnection` class.
    399 
    400 But it's not necessary to edit the source of Trac, the following lines in `trac.wsgi` will also work:
     393=== Trac with PostgreSQL
     394
     395When using the mod_wsgi adapter with multiple Trac instances and PostgreSQL (or MySQL?) as the database, the server ''may'' create a lot of open database connections and thus PostgreSQL processes.
     396
     397A somewhat brutal workaround is to disable connection pooling in Trac. This is done by setting `poolable = False` in `trac.db.postgres_backend` on the `PostgreSQLConnection` class.
     398
     399But it is not necessary to edit the source of Trac. The following lines in `trac.wsgi` will also work:
    401400
    402401{{{#!python
     
    412411}}}
    413412
    414 Now Trac drops the connection after serving a page and the connection count on the database will be kept minimal.
    415 
    416 //This is not a recommended approach though. See also the notes at the bottom of the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac mod_wsgi's IntegrationWithTrac] wiki page.//
     413Now Trac drops the connection after serving a page and the connection count on the database will be kept low.
     414
     415//This is not a recommended approach though. See also the notes at the bottom of the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki mod_wsgi's IntegrationWithTrac] wiki page.//
    417416
    418417=== Other resources
    419418
    420 For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [http://code.google.com/p/modwsgi/wiki/ApplicationIssues application issues] when using mod_wsgi. The wsgi page also has a [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac Integration With Trac] document.
    421 
     419For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [https://code.google.com/archive/p/modwsgi/wikis/ApplicationIssues.wiki application issues] when using mod_wsgi. The wsgi page also has a [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki Integration With Trac] document.
    422420
    423421----
    424 See also:  TracGuide, TracInstall, [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]
     422See also: TracGuide, TracInstall, [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]