tracd fails to authenticate after first successfull login

[ceremcem@…]

1. Use tracd to serve a repository.

1.1. Configure tracd to use htpasswd or htdigest file.

2. Go to trac repository and try to login.
3. Fill the prompt (username, password)

3.1. You will successfully log in.

4. Logout and click to "Login" again.
5. Fill the prompt, click "OK".
6. Go to step 5. as many as you like. If you get bored, continue with step 7.
7. Restart tracd daemon.
8. Go to step 2.

I can not find a work-around for this. I can not continuously restart tracd webserver. I tried to use fcgi, I could authenticate via Nginx as expected but that time I face with another problem while submitting new ticket ("…Do you have cookies enabled?" thing).

This issue also true for Trac 0.11.7.

I'm using Ubuntu Server 11.04 for Trac 0.12.2, Ubuntu Desktop 10.04 for Trac 0.11.7.

[Remy Blank]

Anything in the log when logging in fails that could help us diagnose this?

[Christian Boos]

Also, the fact that you can redo 4./5. multiple times suggests that something strange is going on with your browser. Normally, you won't get the prompt the second time, but you'll directly log in again as the same user (that's a "feature" of how HTTP authentication works, which is usually seen as a huge annoyance, see #791). I'm also not completely ruling out that you actually tried to report that problem ;-)

[Cerem Cem ASLAN <ceremcem@…>]

Replying to rblank:

Anything in the log when logging in fails that could help us diagnose this?

Here is tracd output:

ceremcem@cca-peynir:dev$ tracd --host=127.0.0.1 --port=9090 --basic-auth="*,/home/ceremcem/dev/trac.htpasswd,trac" /home/ceremcem/dev/tracdeneme
Server starting in PID 6945.
Serving on http://127.0.0.1:9090/
/usr/lib/python2.6/dist-packages/psycopg2/__init__.py:54: RuntimeWarning: can't import decimal module probably needed by _psycopg
  RuntimeWarning)
127.0.0.1 - - [15/Feb/2012 17:14:20] "GET /tracdeneme/login HTTP/1.1" 302 -
127.0.0.1 - - [15/Feb/2012 17:14:22] "GET /tracdeneme HTTP/1.1" 200 -
127.0.0.1 - - [15/Feb/2012 17:14:23] "GET /tracdeneme/chrome/site/your_project_logo.png HTTP/1.1" 404 -
127.0.0.1 - - [15/Feb/2012 17:14:23] "GET /tracdeneme/chrome/common/js/jquery.js HTTP/1.1" 404 -
127.0.0.1 - - [15/Feb/2012 17:14:23] "GET /tracdeneme/chrome/site/your_project_logo.png HTTP/1.1" 404 -
b/2012 17:14:23] "GET /tracdeneme/chrome/site/your_project_logo.png HTTP/1.1" 404 -
127.0.0.1 - - [15/Feb/2012 17:16:49] "GET /tracdeneme/logout HTTP/1.1" 302 -
127.0.0.1 - - [15/Feb/2012 17:16:49] "GET /tracdeneme HTTP/1.1" 200 -
127.0.0.1 - - [15/Feb/2012 17:16:49] "GET /tracdeneme/chrome/common/js/jquery.js HTTP/1.1" 404 -
127.0.0.1 - - [15/Feb/2012 17:16:49] "GET /tracdeneme/chrome/site/your_project_logo.png HTTP/1.1" 404 -

As expected until now. Here we go with the same credentials:

127.0.0.1 - - [15/Feb/2012 17:17:03] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:12] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:18] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:19] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:20] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:21] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:22] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:23] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:23] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:24] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:25] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:26] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:27] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:28] "GET /tracdeneme/login HTTP/1.1" 401 -
127.0.0.1 - - [15/Feb/2012 17:17:28] "GET /tracdeneme/login HTTP/1.1" 401 -

[Cerem Cem ASLAN <ceremcem@…>]

Hmm… Unexpectedly, the bug disappeared o_O (A restart which I did some time ago might cause the bug has been disappear…)