Changes between Version 4 and Version 5 of TracOnWindowsIisPyISAPIe

Timestamp:

Jun 27, 2011, 1:18:29 PM (13 years ago)

Author:

aakoshh@…

Comment:

—

TracOnWindowsIisPyISAPIe

@@ -93 +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
 1. To support authentication, create an empty directory in the base Trac virtual directory in IIS and name it "login". Set directory security to Digest Authentication (it works behind Nginx, whereas Integrated Windows Authentication does not). 
-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" with capital letters, and the roles defined were picked up only for the one that I explicitly granted it for with trac-admin. Whichever appears on the site, add permissions for that username like this: {{trac-admin $ENV permission add DOMAIN\user TRAC_ADMIN}}
+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" with capital letters, and the roles defined were picked up only for the one that I explicitly granted it for with trac-admin. Whichever appears on the site, add permissions for that username like this: {{{trac-admin $ENV permission add DOMAIN\user TRAC_ADMIN}}}
 1. 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:
 {{{