Edgewall Software

Changes between Version 2 and Version 3 of TracOnWindowsIisPyISAPIe


Ignore:
Timestamp:
Jun 27, 2011, 1:13:05 PM (13 years ago)
Author:
anonymous
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TracOnWindowsIisPyISAPIe

    v2 v3  
    9191}}}
    92921. After changes are made to either Python modules or the trac.ini file, right click on the application pool and click recycle. The site should display at this point.
    93 1. I had some problems with static files (Trac css and Javascript) over 4K in size not being served. The exception seems to be raised when the content length header is set in StartResponse above, maybe it is sent twice. I ended up setting up an IIS virtual directory to serve the htdocs directory of Trac and added the htdocs_location = /trac_media entry to trac.ini
     931. I had some problems with static files (Trac css and Javascript) over 4K in size not being served. The exception seems to be raised when the content length header is set in {{{StartResponse}}} above, maybe it is sent twice. I ended up setting up an IIS virtual directory to serve the htdocs directory of Trac and added the htdocs_location = /trac_media entry to trac.ini
    94941. create a virtual directory under the base Trac site in IIS and name it "login". Set directory security to Digest Authentication, it works behing Nginx. 1. I had some trouble with the admin account: when I accessed the site directly by IP and logged in with my Windows credentials, the remote user was "domain\user", but through our router it became "DOMAIN\user", and the roles defined were picked up only for the one explicitly granted. Whichever appears on the site, add permissions for that username like this: "trac-admin $ENV permission add DOMAIN\user TRAC_ADMIN"
    95951. The header and footer did not appear on Trac pages (it did in the standalone server). I had to modify layout.html and remove the fallback tag at the bottom of the document like this: