Edgewall Software

Changes between Version 1 and Version 2 of TracOnWindowsIisPyISAPIe


Ignore:
Timestamp:
Jun 27, 2011, 1:10:39 PM (13 years ago)
Author:
aakoshh@…
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TracOnWindowsIisPyISAPIe

    v1 v2  
    6060
    6161}}}
    62 1. Edit the WSGI.py module in the Http directory and uncomment REMOTE_USER in the IsapeEnvAuto list so that Trac can pick up the logged in user.
    63 1. When there is an error, Trac tries to present its error.html template, but also passes the exception info to the WSGI function "start_response". PyISAPIe, however, re-raises the exception even though it was handled, so for example unhandled paths result in an IIS Internal Error page and a stack trace. I edited the WSGI.py again so that if Trac supports an exception info but headers are also present, no exception is raised to IIS:
     621. Edit the WSGI.py module in the Http directory and uncomment REMOTE_USER in the {{{IsapeEnvAuto}}} list so that Trac can pick up the logged in user.
     631. When there is an error, Trac tries to present its error.html template, but also passes the exception info to the WSGI function {{{start_response}}}. PyISAPIe, however, re-raises the exception even though it was handled, so for example unhandled paths result in an IIS Internal Error page and a stack trace. I edited the WSGI.py again so that if Trac supports an exception info but headers are also present, no exception is raised to IIS:
    6464{{{
    6565def StartResponse(Status, Headers, ExcInfo = None):