Opened 19 years ago
Closed 17 years ago
#3048 closed defect (fixed)
Issue with redirect after login
Reported by: | Owned by: | osimons | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11 |
Component: | general | Version: | devel |
Severity: | normal | Keywords: | path login referer |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Regarding trunk/trac/web/auth.py@3174#L190 - auth.py / LoginModule / def _redirect_back(self.req)
The test for "same site" is not quite sufficient, as it will get the result wrong when directly linking to /login when one projectname is a substring of another. A simple example is "sandbox" and "sandbox2". It actually gives errors both ways:
- Link from sandbox to sandbox2/login will get you to the project, but not actually logged in properly. Why this happens, I have not been able to figure out. It just sees me as 'anonymous', even after doing the "login" link manually afterwards. Any ideas? Something else comparing projectnames giving false positives? I have a "home" module that I've made for front page replacement (default component), but it does not receive the authentication information. It is build to "Trac standards", and doesn't do anything complicated that should suggest a problem here.
- Linking from /sandbox2 to /sandbox/login will actually not take you anywhere, as it does not get caught by the if-test (substring match). The redirect back does not make sense. I made a small change to the if-test, and this issue seems to work correctly:
if referer and not (referer == req.base_url \ or referer.startswith(req.base_url + '/')):
This fix for issue 2 will catch both where the referrer is just /sandbox2 (no specific module/page) and where it is like /sandbox2/wiki/WikiStart (by closing the projectname with a '/' testing for /sandbox/).
I have made a cross-project personalised navigation, and have no issues of any kind with projects that are not substrings of each other.
Attachments (0)
Change History (5)
comment:1 by , 18 years ago
Keywords: | path login referer added |
---|---|
Severity: | normal → major |
Version: | 0.9.4 → devel |
follow-up: 3 comment:2 by , 18 years ago
Keywords: | verify added |
---|---|
Milestone: | → 0.10.5 |
Verify how the fix for #2553 would affect this one.
comment:3 by , 17 years ago
Keywords: | verify removed |
---|---|
Milestone: | 0.10.5 → 0.11.1 |
Owner: | changed from | to
comment:4 by , 17 years ago
Milestone: | 0.11.1 → 0.11 |
---|---|
Status: | new → assigned |
OK, the original patch still solves this, but using the rstrip()
from first comment to make the matching correct. I'd go with the harmless approach here though, and not add more than a correct matching of projectname, leaving the redirect working as before:
-
trac/web/auth.py
198 198 def _redirect_back(self, req): 199 199 """Redirect the user back to the URL she came from.""" 200 200 referer = req.get_header('Referer') 201 if referer and not referer.startswith(req.base_url): 201 if referer and not (referer == req.base_url or \ 202 referer.startswith(req.base_url.rstrip('/')+'/')): 202 203 # only redirect to referer if it is from the same site 203 204 referer = None 204 205 req.redirect(referer or req.abs_href())
If no one objects or has a better approach, I'll commit it.
comment:5 by , 17 years ago
Resolution: | → fixed |
---|---|
Severity: | major → normal |
Status: | assigned → closed |
Patch for issue 2) applied in [6279]. Closing.
I think to be correct, you would have to look like this:
Though, this doesn't fix the problem that if login or logout are in https://, while the main site is in http:// and you don't write stupid RewriteRules to bounce the user back (why do that, anyway?)…
I'll happily do a patch for this, if someone wants (I actually already have one).
You can reach me at http://docwhat.gerf.org/ The email is the same as the hostname but the first dot is an at-sign.
Ciao!