Where is trac.fcgi

Or maybe anyone directly has a solution? And I didn't thought I would have got broken files from the trac poject But that's the case, thanks to support of my hoster uberspace. So, a simple dos2unix trag. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Asked 8 years, 3 months ago. Active 6 years, 8 months ago. Viewed 1k times.

Improve this question. Add a comment. Opened 15 years ago. Closed 14 years ago. Last modified 9 years ago. Doesn't look like the Accountmanager plugin's password file is being consulted, as per your page's declaration that AccountManagerplugin is used to check passwords.

Standard form-based login still works. They both result in a login dialog. Snooping source, I see log entries It seems that something The AccountManager plugin? Thought maybe I was crazy so I tcpdumped this from the server; the Authorization header is definitely received by Apache. Somewhere along the line it must be stripped out but I'm having a devil of a time trying to find where. I had the same problem.

In my case the problem was that the header "Authorization" doesn't arrive to the cgi or fcgi. I could get it in the. The second one is the normal rule for Trac. The first one is an special adaption of the second one: when the header "Athorization" is present in a request and starts with "Basic" I rewrite the url to pass an argument to the cgi.

I pass as argument the value of the header Athorization. So, the next step is to get this argument in the cgi. This variable will be used then by the HttpAuthPlugin.

I had a lot of trouble with the solution as stated above, eventually I came up with a slightly modified version which suited my environment. Here are the relavent sections of the apache 2. Please note that Mylyn should support form-based authentication via the AccountManagerPlugin in the latest releases. But this cannot be used in Directory or Location context, which makes it difficult to support multiple projects. A better method which works for both of these modules and for lighttpd and CGI as well , because it involves no server configuration settings for environment variables, is to set one of the variables in trac.

Using this method, different projects can be supported by using different. See this fcgid example config which uses a ScriptAlias directive with trac. The FastCGI front-end was developed primarily for use with alternative webservers, such as lighttpd. It has a very low memory footprint compared to other web servers and takes care of CPU load.

Note that you will need to add a new entry to fastcgi. Note that field values are different. If you prefer setting the environment variables in the.

Note that the above will result in different processes in any event, even if both are running from the same trac.

Note from c00i90wn: It's very important the order on which server.