Changes between Version 6 and Version 7 of TracModPython


Ignore:
Timestamp:
08/08/15 13:07:50 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracModPython

    v6 v7  
    1 = Trac and mod_python = 
    21[[TracGuideToc]] 
    32 
     3= Trac and mod_python 
     4 
     5Mod_python is an [https://httpd.apache.org/ Apache] module that embeds the Python interpreter within the server, so that web-based applications in Python will run many times faster than traditional CGI and will have the ability to retain database connections. 
    46Trac supports [http://www.modpython.org/ mod_python], which speeds up Trac's response times considerably, especially compared to [TracCgi CGI], and permits use of many Apache features not possible with [wiki:TracStandalone tracd]/mod_proxy. 
    57 
    6 {{{#!div class="important" 
    7 ** A Word of Warning ** 
    8  
    9 As of 16^th^ June 2010, the mod_python project is officially dead.  If you are considering using mod_python for a new installation, '''please don't'''!  There are known issues which will not be fixed and there are now better alternatives.  Check out the main TracInstall pages for your target version for more information. 
    10 }}} 
    11  
    12  
    13 These instructions are for Apache 2; if you are still using Apache 1.3, you may have some luck with [trac:wiki:TracModPython2.7 TracModPython2.7], but you'll be totally on your own. 
     8These instructions are for Apache 2. If you are using Apache 1.3, you may have some luck with [trac:wiki:TracModPython2.7 TracModPython2.7], but that is a deprecated setup. 
    149 
    1510[[PageOutline(2-3,Overview,inline)]] 
     
    1813 
    1914If you just installed mod_python, you may have to add a line to load the module in the Apache configuration: 
    20 {{{ 
     15{{{#!apache 
    2116LoadModule python_module modules/mod_python.so 
    2217}}} 
    2318 
    24 ''Note: The exact path to the module depends on how the HTTPD installation is laid out.'' 
    25  
    26 On Debian using apt-get 
    27 {{{ 
     19'''Note''': The exact path to the module depends on how the HTTPD installation is laid out. 
     20 
     21On Debian using apt-get: 
     22{{{#!sh 
    2823apt-get install libapache2-mod-python libapache2-mod-python-doc 
    2924}}} 
    30 (Still on Debian) after you have installed mod_python, you must enable the modules in apache2 (equivalent of the above Load Module directive): 
    31 {{{ 
     25 
     26Still on Debian, after you have installed mod_python, you must enable the modules in apache2, equivalent to the above Load Module directive: 
     27{{{#!sh 
    3228a2enmod python 
    3329}}} 
     30 
    3431On Fedora use, using yum: 
    35 {{{ 
     32{{{#!sh 
    3633yum install mod_python 
    3734}}} 
    38 You can test your mod_python installation by adding the following to your httpd.conf.  You should remove this when you are done testing for security reasons. Note: mod_python.testhandler is only available in mod_python 3.2+. 
    39 {{{ 
    40 #!xml 
     35 
     36You can test your mod_python installation by adding the following to your httpd.conf. You should remove this when you are done testing for security reasons. Note: mod_python.testhandler is only available in mod_python 3.2+. 
     37{{{#!apache 
    4138<Location /mpinfo> 
    4239   SetHandler mod_python 
     
    4946 
    5047A simple setup of Trac on mod_python looks like this: 
    51 {{{ 
    52 #!xml 
     48{{{#!apache 
    5349<Location /projects/myproject> 
    5450   SetHandler mod_python 
     
    6258}}} 
    6359 
    64 The option '''`TracUriRoot`''' may or may not be necessary in your setup. Try your configuration without it; if the URLs produced by Trac look wrong, if Trac does not seem to recognize URLs correctly, or you get an odd "No handler matched request to..." error, add the '''`TracUriRoot`''' option.  You will notice that the `Location` and '''`TracUriRoot`''' have the same path. 
    65  
    66 The options available are 
    67 {{{ 
    68     # For a single project 
    69     PythonOption TracEnv /var/trac/myproject 
    70  
    71     # For multiple projects 
    72     PythonOption TracEnvParentDir /var/trac/myprojects 
    73  
    74     # For the index of multiple projects 
    75     PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_template.html 
    76  
    77     # A space delimitted list, with a "," between key and value pairs. 
    78     PythonOption TracTemplateVars key1,val1 key2,val2 
    79  
    80     # Useful to get the date in the wanted order 
    81     PythonOption TracLocale en_GB.UTF8 
    82  
    83     # See description above         
    84     PythonOption TracUriRoot /projects/myproject 
    85 }}} 
    86  
    87 === Python Egg Cache === 
    88  
    89 Compressed python eggs like Genshi are normally extracted into a directory named `.python-eggs` in the users home directory. Since apache's home usually is not writable an alternate egg cache directory can be specified like this: 
    90 {{{ 
     60The option '''`TracUriRoot`''' may or may not be necessary in your setup. Try your configuration without it; if the URLs produced by Trac look wrong, if Trac does not seem to recognize URLs correctly, or you get an odd "No handler matched request to..." error, add the '''`TracUriRoot`''' option. You will notice that the `Location` and '''`TracUriRoot`''' have the same path. 
     61 
     62The options available are: 
     63{{{#!apache 
     64# For a single project 
     65PythonOption TracEnv /var/trac/myproject 
     66 
     67# For multiple projects 
     68PythonOption TracEnvParentDir /var/trac/myprojects 
     69 
     70# For the index of multiple projects 
     71PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_template.html 
     72 
     73# A space delimitted list, with a "," between key and value pairs. 
     74PythonOption TracTemplateVars key1,val1 key2,val2 
     75 
     76# Useful to get the date in the wanted order 
     77PythonOption TracLocale en_GB.UTF8 
     78 
     79# See description above         
     80PythonOption TracUriRoot /projects/myproject 
     81}}} 
     82 
     83=== Python Egg Cache 
     84 
     85Compressed Python eggs like Genshi are normally extracted into a directory named `.python-eggs` in the users home directory. Since Apache's home usually is not writeable, an alternate egg cache directory can be specified like this: 
     86{{{#!apache 
    9187PythonOption PYTHON_EGG_CACHE /var/trac/myprojects/egg-cache 
    9288}}} 
    9389 
    94 or you can uncompress the Genshi egg to resolve problems extracting from it. 
    95  
    96 === Configuring Authentication === 
     90Or you can uncompress the Genshi egg to resolve problems extracting from it. 
     91 
     92=== Configuring Authentication 
    9793 
    9894See corresponding section in the [wiki:TracModWSGI#ConfiguringAuthentication] page. 
    9995 
    100  
    10196== Advanced Configuration 
    10297 
    103 === Setting the Python Egg Cache === 
    104  
    105 If the Egg Cache isn't writeable by your Web server, you'll either have to change the permissions, or point Python to a location where Apache can write. This can manifest itself as a ''500 internal server error'' and/or a complaint in the syslog.  
    106  
    107 {{{ 
    108 #!xml 
     98=== Setting the Python Egg Cache 
     99 
     100If the Egg Cache isn't writeable by your Web server, you'll either have to change the permissions, or point Python to a location where Apache can write. This can manifest itself as a `500 internal server error` and/or a complaint in the syslog.  
     101 
     102{{{#!apache 
    109103<Location /projects/myproject> 
    110104  ... 
     
    114108}}} 
    115109 
    116  
    117 === Setting the !PythonPath === 
    118  
    119 If the Trac installation isn't installed in your Python path, you'll have to tell Apache where to find the Trac mod_python handler  using the `PythonPath` directive: 
    120 {{{ 
    121 #!xml 
     110=== Setting the !PythonPath 
     111 
     112If the Trac installation isn't installed in your Python path, you will have to tell Apache where to find the Trac mod_python handler  using the `PythonPath` directive: 
     113{{{#!apache 
    122114<Location /projects/myproject> 
    123115  ... 
     
    129121Be careful about using the !PythonPath directive, and ''not'' `SetEnv PYTHONPATH`, as the latter won't work. 
    130122 
    131 === Setting up multiple projects === 
     123=== Setting up multiple projects 
    132124 
    133125The Trac mod_python handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`: 
    134 {{{ 
    135 #!xml 
     126{{{#!apache 
    136127<Location /projects> 
    137128  SetHandler mod_python 
     
    146137 
    147138If you don't want to have the subdirectory listing as your projects home page you can use a 
    148 {{{ 
    149 #!xml 
     139{{{#!apache 
    150140<LocationMatch "/.+/"> 
    151141}}} 
     
    154144 
    155145You can also use the same authentication realm for all of the projects using a `<LocationMatch>` directive: 
    156 {{{ 
    157 #!xml 
     146{{{#!apache 
    158147<LocationMatch "/projects/[^/]+/login"> 
    159148  AuthType Basic 
     
    164153}}} 
    165154 
    166 === Virtual Host Configuration === 
    167  
    168 Below is the sample configuration required to set up your trac as a virtual server (i.e. when you access it at the URLs like 
    169 !http://trac.mycompany.com): 
    170  
    171 {{{ 
    172 #!xml 
    173 <VirtualHost * > 
     155=== Virtual Host Configuration 
     156 
     157Below is the sample configuration required to set up your Trac as a virtual server, ie when you access it at the URLs like 
     158`http://trac.mycompany.com`: 
     159 
     160{{{#!apache 
     161<VirtualHost *> 
    174162    DocumentRoot /var/www/myproject 
    175163    ServerName trac.mycompany.com 
     
    191179 
    192180This does not seem to work in all cases. What you can do if it does not: 
    193  * Try using `<LocationMatch>` instead of `<Location>` 
    194  * <Location /> may, in your server setup, refer to the complete host instead of simple the root of the server. This means that everything (including the login directory referenced below) will be sent to python and authentication does not work (i.e. you get the infamous Authentication information missing error). If this applies to you, try using a sub-directory for trac instead of the root (i.e. /web/ and /web/login instead of / and /login). 
     181 * Try using `<LocationMatch>` instead of `<Location>`. 
     182 * `<Location />` may, in your server setup, refer to the complete host instead of simple the root of the server. This means that everything (including the login directory referenced below) will be sent to Python and authentication does not work, ie you get the infamous Authentication information missing error. If this is the case, try using a sub-directory for Trac instead of the root, ie /web/ and /web/login instead of / and /login. 
    195183 * Depending on apache's `NameVirtualHost` configuration, you may need to use `<VirtualHost *:80>` instead of `<VirtualHost *>`. 
    196184 
    197 For a virtual host that supports multiple projects replace "`TracEnv`" /var/trac/myproject with "`TracEnvParentDir`" /var/trac/ 
    198  
    199 Note: !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserver bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment". 
    200  
    201 == Troubleshooting == 
    202  
    203 In general, if you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option: 
    204 {{{ 
    205 #!xml 
     185For a virtual host that supports multiple projects replace `TracEnv /var/trac/myproject` with `TracEnvParentDir /var/trac`. 
     186 
     187'''Note''': !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserver bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment". 
     188 
     189== Troubleshooting 
     190 
     191If you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option: 
     192{{{#!apache 
    206193<Location /projects/myproject> 
    207194  ... 
     
    212199For multiple projects, try restarting the server as well. 
    213200 
    214 === Login Not Working === 
     201=== Login Not Working 
     202 
    215203If you've used `<Location />` directive, it will override any other directives, as well as `<Location /login>`. 
    216204The workaround is to use negation expression as follows (for multi project setups): 
    217 {{{ 
    218 #!xml 
     205{{{#!apache 
    219206#this one for other pages 
    220207<Location ~ "/*(?!login)"> 
     
    223210   PythonOption TracEnvParentDir /projects 
    224211   PythonOption TracUriRoot / 
    225  
    226 </Location> 
     212</Location> 
     213 
    227214#this one for login page 
    228215<Location ~ "/[^/]+/login"> 
     
    247234 
    248235This problem will most certainly hit you on Unix when using Python 2.4. 
    249 In Python 2.4, some version of Expat (an XML parser library written in C) is used,  
    250 and if Apache is using another version, this results in segmentation faults. 
    251 As Trac 0.11 is using Genshi, which will indirectly use Expat, that problem 
    252 can now hit you even if everything was working fine before with Trac 0.10. 
    253  
    254 See Graham Dumpleton's detailed [http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash explanation and workarounds] for the issue. 
    255  
    256 === Form submission problems === 
     236In Python 2.4, some version of [http://expat.sourceforge.net/ Expat] (an XML parser library written in C) is used and if Apache is using another version, this results in segmentation faults. 
     237As Trac 0.11 is using Genshi, which will indirectly use Expat, that problem can now hit you even if everything was working fine before with Trac 0.10. This problem has not been reported for Python 2.5+, so best to upgrade. 
     238 
     239=== Form submission problems 
    257240 
    258241If you're experiencing problems submitting some of the forms in Trac (a common problem is that you get redirected to the start page after submission), check whether your {{{DocumentRoot}}} contains a folder or file with the same path that you mapped the mod_python handler to. For some reason, mod_python gets confused when it is mapped to a location that also matches a static resource. 
    259242 
    260 === Problem with virtual host configuration === 
    261  
    262 If the <Location /> directive is used, setting the `DocumentRoot` may result in a ''403 (Forbidden)'' error. Either remove the `DocumentRoot` directive, or make sure that accessing the directory it points is allowed (in a corresponding `<Directory>` block). 
    263  
    264 Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able download any CSS or images/icons. I used <Location /trac> `SetHandler None` </Location> to circumvent the problem, though I do not know if this is the most elegant solution. 
    265  
    266 === Problem with zipped egg === 
    267  
    268 It's possible that your version of mod_python will not import modules from zipped eggs. If you encounter an `ImportError: No module named trac` in your Apache logs but you think everything is where it should be, this might be your problem. Look in your site-packages directory; if the Trac module appears as a ''file'' rather than a ''directory'', then this might be your problem. To rectify, try installing Trac using the `--always-unzip` option, like this: 
    269  
    270 {{{ 
     243=== Problem with virtual host configuration 
     244 
     245If the <Location /> directive is used, setting the `DocumentRoot` may result in a ''403 (Forbidden)'' error. Either remove the `DocumentRoot` directive, or make sure that accessing the directory it points is allowed, in a corresponding `<Directory>` block. 
     246 
     247Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able to download any CSS or images/icons. Use <Location /trac> `SetHandler None` </Location> to circumvent the problem, though this may not be the most elegant solution. 
     248 
     249=== Problem with zipped egg 
     250 
     251It's possible that your version of mod_python will not import modules from zipped eggs. If you encounter an `ImportError: No module named trac` in your Apache logs but you think everything is where it should be, this might be your problem. Look in your site-packages directory; if the Trac module appears as a ''file'' rather than a ''directory'', then this might be your problem. To rectify this, try installing Trac using the `--always-unzip` option: 
     252 
     253{{{#!sh 
    271254easy_install --always-unzip Trac-0.12b1.zip 
    272255}}} 
    273256 
    274 === Using .htaccess === 
     257=== Using .htaccess 
    275258 
    276259Although it may seem trivial to rewrite the above configuration as a directory in your document root with a `.htaccess` file, this does not work. Apache will append a "/" to any Trac URLs, which interferes with its correct operation. 
    277260 
    278 It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth. Stick to the provided instructions. :) 
    279  
    280 A success story: For me it worked out-of-box, with following trivial config: 
    281 {{{#!xml 
     261It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth. 
     262 
     263This also works out-of-box, with following trivial config: 
     264{{{#!apache 
    282265SetHandler mod_python 
    283266PythonInterpreter main_interpreter 
     
    292275}}} 
    293276 
    294 The `TracUriRoot` is obviously the path you need to enter to the browser to get to the trac (e.g. domain.tld/projects/trac) 
    295  
    296 === Additional .htaccess help === 
    297  
    298 If you are using the .htaccess method you may have additional problems if your trac directory is inheriting .htaccess directives from another. This may also help to add to your .htaccess file: 
    299  
    300 {{{ 
     277The `TracUriRoot` is obviously the path you need to enter to the browser to get to Trac, eg `domain.tld/projects/trac`. 
     278 
     279=== Additional .htaccess help 
     280 
     281If you are using the .htaccess method you may have additional problems if your Trac directory is inheriting .htaccess directives from another. This may also help to add to your .htaccess file: 
     282 
     283{{{#!apache 
    301284<IfModule mod_rewrite.c> 
    302285  RewriteEngine Off 
     
    305288 
    306289=== Platform specific issues 
    307 ==== Win32 Issues ==== 
    308 If you run trac with mod_python < 3.2 on Windows, uploading attachments will '''not''' work. This problem is resolved in mod_python 3.1.4 or later, so please upgrade mod_python to fix this. 
    309  
    310  
    311 ==== OS X issues ==== 
    312  
    313 When using mod_python on OS X you will not be able to restart Apache using `apachectl restart`. This is apparently fixed in mod_python 3.2, but there's also a patch available for earlier versions [http://www.dscpl.com.au/projects/vampire/patches.html here]. 
    314  
    315 ==== SELinux issues ==== 
    316  
    317 If Trac reports something like: ''Cannot get shared lock on db.lock'' 
    318 The security context on the repository may need to be set: 
    319  
    320 {{{ 
     290==== Win32 Issues 
     291 
     292If you run Trac with mod_python < 3.2 on Windows, uploading attachments will '''not''' work. This problem is resolved in mod_python 3.1.4 or later, so please upgrade mod_python to fix this. 
     293 
     294==== OS X issues 
     295 
     296When using mod_python on OS X you will not be able to restart Apache using `apachectl restart`. This is apparently fixed in mod_python 3.2, so please upgrade mod_python to fix this. 
     297 
     298==== SELinux issues 
     299 
     300If Trac reports something like: `Cannot get shared lock on db.lock`, then the security context on the repository may need to be set: 
     301 
     302{{{#!sh 
    321303chcon -R -h -t httpd_sys_content_t PATH_TO_REPOSITORY 
    322304}}} 
    323305 
    324 See also [http://subversion.tigris.org/faq.html#reposperms] 
    325  
    326 ==== FreeBSD issues ==== 
    327 Pay attention to the version of the installed mod_python and sqlite packages. Ports have both the new and old ones, but earlier versions of pysqlite and mod_python won't integrate as the former requires threaded support in python, and the latter requires a threadless install. 
    328  
    329 If you compiled and installed apache2, apache wouldn´t support threads (cause it doesn´t work very well on FreeBSD). You could force thread support when running ./configure for apache, using --enable-threads, but this isn´t recommendable. 
    330 The best option [http://modpython.org/pipermail/mod_python/2006-September/021983.html seems to be] adding to /usr/local/apache2/bin/ennvars the line  
    331  
    332 {{{ 
     306See also [http://subversion.apache.org/faq.html#reposperms How do I set repository permissions correctly?] 
     307 
     308==== FreeBSD issues 
     309 
     310The FreeBSD ports have both the new and old versions of mod_python and SQLite, but earlier versions of pysqlite and mod_python won't integrate: 
     311 * pysqlite requires threaded support in Python 
     312 * mod_python requires a threadless install. 
     313 
     314Apache2 does not automatically support threads on FreeBSD. You could force thread support when running `./configure` for Apache, using `--enable-threads`, but this isn´t recommended. 
     315The best option [http://modpython.org/pipermail/mod_python/2006-September/021983.html seems to be] adding to /usr/local/apache2/bin/ennvars the line: 
     316 
     317{{{#!sh 
    333318export LD_PRELOAD=/usr/lib/libc_r.so 
    334319}}} 
    335320 
    336  
    337 ==== Fedora 7 Issues ==== 
    338 Make sure you install the 'python-sqlite2' package as it seems to be required for TracModPython but not for tracd 
    339  
    340  
    341 === Subversion issues === 
    342  
    343 If you get the following Trac Error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive. (The better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory.) 
    344  
    345 If this is not the case, it's possible that you're using Subversion libraries that are binary incompatible with the apache ones (an incompatibility of the `apr` libraries is usually the cause). In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`). 
    346  
    347 You also need a recent version of `mod_python` in order to avoid a runtime error ({{{argument number 2: a 'apr_pool_t *' is expected}}}) due to the default usage of multiple sub-interpreters. 3.2.8 ''should'' work, though it's probably better to use the workaround described in [trac:#3371 #3371], in order to force the use of the main interpreter: 
    348 {{{ 
     321==== Fedora 7 Issues 
     322 
     323Make sure you install the 'python-sqlite2' package as it seems to be required for TracModPython, but not for tracd. 
     324 
     325=== Subversion issues 
     326 
     327If you get the following Trac error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive. A better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory. 
     328 
     329If this is not the case, it's possible that you are using Subversion libraries that are binary incompatible with the Apache ones and an incompatibility of the `apr` libraries is usually the cause. In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`). 
     330 
     331You also need a recent version of `mod_python` in order to avoid a runtime error ({{{argument number 2: a 'apr_pool_t *' is expected}}}) due to the default usage of multiple sub-interpreters. Version 3.2.8 ''should'' work, though it's probably better to use the workaround described in [trac:#3371 #3371], in order to force the use of the main interpreter: 
     332{{{#!apache 
    349333PythonInterpreter main_interpreter 
    350334}}} 
    351 This is anyway the recommended workaround for other well-known issues seen when using the Python bindings for Subversion within mod_python ([trac:#2611 #2611], [trac:#3455 #3455]). See in particular Graham Dumpleton's comment in [trac:comment:9:ticket:3455 #3455] explaining the issue. 
    352  
    353 === Page layout issues === 
    354  
    355 If the formatting of the Trac pages look weird chances are that the style sheets governing the page layout are not handled properly by the web server. Try adding the following lines to your apache configuration: 
    356 {{{ 
    357 #!xml 
     335 
     336This is also the recommended workaround for other issues seen when using the Python bindings for Subversion within mod_python ([trac:#2611 #2611], [trac:#3455 #3455]). See in particular Graham Dumpleton's comment in [trac:comment:9:ticket:3455 #3455] explaining the issue. 
     337 
     338=== Page layout issues 
     339 
     340If the formatting of the Trac pages look weird, chances are that the style sheets governing the page layout are not handled properly by the web server. Try adding the following lines to your Apache configuration: 
     341{{{#!apache 
    358342Alias /myproject/css "/usr/share/trac/htdocs/css" 
    359343<Location /myproject/css> 
     
    362346}}} 
    363347 
    364 Note: For the above configuration to have any effect it must be put after the configuration of your project root location, i.e. {{{<Location /myproject />}}}. 
    365  
    366 Also, setting `PythonOptimize On` seems to mess up the page headers and footers, in addition to hiding the documentation for macros and plugins (see #Trac8956). Considering how little effect the option has, it is probably a good idea to leave it `Off`. 
    367  
    368 === HTTPS issues === 
    369  
    370 If you want to run Trac fully under https you might find that it tries to redirect to plain http. In this case just add the following line to your apache configuration: 
    371 {{{ 
    372 #!xml 
    373 <VirtualHost * > 
     348'''Note''': For the above configuration to have any effect it must be put after the configuration of your project root location, ie {{{<Location /myproject />}}}. 
     349 
     350Also, setting `PythonOptimize On` seems to mess up the page headers and footers, in addition to hiding the documentation for macros and plugins (see #Trac8956). Considering how little effect the option has, leave it `Off`. 
     351 
     352=== HTTPS issues 
     353 
     354If you want to run Trac fully under https you might find that it tries to redirect to plain http. In this case just add the following line to your Apache configuration: 
     355{{{#!apache 
     356<VirtualHost *> 
    374357    DocumentRoot /var/www/myproject 
    375358    ServerName trac.mycompany.com 
     
    379362}}} 
    380363 
    381  
    382 === Segmentation fault with php5-mhash or other php5 modules === 
    383 You may encounter segfaults (reported on debian etch) if php5-mhash module is installed. Try to remove it to see if this solves the problem. See debian bug report [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411487] 
    384  
    385 Some people also have troubles when using php5 compiled with its own 3rd party libraries instead of system libraries. Check here [http://www.djangoproject.com/documentation/modpython/#if-you-get-a-segmentation-fault] 
     364=== Segmentation fault with php5-mhash or other php5 modules 
     365 
     366You may encounter segfaults (reported on Debian etch) if php5-mhash module is installed. Try to remove it to see if this solves the problem. See [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411487 Debian bug report]. 
     367 
     368Some people also have troubles when using PHP5 compiled with its own third party libraries instead of system libraries. Check [http://www.djangoproject.com/documentation/modpython/#if-you-get-a-segmentation-fault Django segmentation fault]. 
    386369 
    387370---- 
    388 See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI],  [trac:TracNginxRecipe TracNginxRecipe] 
     371See also: TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [trac:TracNginxRecipe]