Issue 1190187
Created on 2005-04-26 11:40 by anonymous, last changed 2005-06-24 05:23 by richard.
| msg1935 |
Author: [hidden] (anonymous) |
Date: 2005-04-26 11:40 |
|
I have following scenario:
roundup tracker (0.8.2) running on localhost, apache +
mod_rewrite is proxying the requests and mapping the
tracker to a server's URL namespace.
Tracker is accessible from the Internet without any
authorization. This works fine. In order to access the
tracker from the Internet, one has to authorize against
apache (and then, the user is allowed to login to
roundup). The access from the Internet worked fine in
previous releases (0.7.X), but 0.8.X contains "support"
for HTTP_AUTHORIZATION (roundup/cgi/client.py:400 ...),
which breaks the things if:
1) webserver passes REMOTE_USER and HTTP_AUTHORIZATION
variables to roundup
2) REMOTE_USER has a password different to his password
in roundup.
Please provide a configuration option, which will
enable/disable HTTP_AUTH. With the current code and my
config, roundup responses with 403 HTTP responsecode.
|
| msg1936 |
Author: [hidden] (richard) |
Date: 2005-06-24 05:23 |
|
Logged In: YES
user_id=6405
I will assume that in 2) above you meant to say "REMOTE_USER
has a username different to his username in roundup."
Fix will be present in 0.8.4
|
|
| Date |
User |
Action |
Args |
| 2005-04-26 11:40:21 | anonymous | create | |
|