#7451 closed defect (invalid)
Strange login redirect behavior
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.11 |
| Severity: | normal | Keywords: | needinfo |
| Cc: | daniel@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Since http://svn.boost.org upgraded to 0.11, I've seen a change in behavior. It used to be that I could click "new ticket," then notice I'm not logged in, then log in and still be looking at the new ticket form. Since the upgrade to 0.11, when I log in, I am redirected to the main wiki page.
I have a feeling this may be related to why the LoginRedirect plugin doesn't work on my own Trac instance (a different one).
I can create a login for testing purposes on svn.boost.org if you need to experience this for yourself.
Attachments (0)
Change History (6)
comment:1 by , 16 years ago
| Cc: | added |
|---|
comment:2 by , 16 years ago
| Cc: | removed |
|---|---|
| Keywords: | needinfo added |
Is this still an issue with 0.11.1? The "new ticket" case mentioned in the description seems to work here, at least.
comment:3 by , 16 years ago
| Cc: | added |
|---|
I don't know whether it's still an issue with 0.11.1 because I personally can't upgrade http://svn.boost.org. However, I've Cc'd people who can, so maybe we can get an answer.
comment:4 by , 16 years ago
| Cc: | removed |
|---|
Well, apparently I can't edit the Cc's, but I sent them mail pointing to this ticket.
comment:5 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Fixed now; seems like this particular issue was on the server side all along. Sorry for the noise.
comment:6 by , 16 years ago
What was the solution? We are seeing this on our Sage trac (http://www.sagemath.org) as well.
I have added a patch to #5340 that adds redirection to
/loginwhen accessing a restricted resource unauthenticated. The reason why th:PermRedirectPlugin doesn't work is because when it redirects to/login, theReferer:header is empty or missing instead of containing the original URL.You might want to try the patch and see if it solves the problem for you.