-
Bug
-
Resolution: Fixed
-
Low
-
6.14.0
-
Severity 3 - Minor
-
Issue Summary
Confluence Search return "Something went wrong" after session timed out instead of redirecting user to Login page.
Environment
Confluence version 6.14.0
Steps to Reproduce
- Login into Confluence.
- Open a new browser tab and access any Confluence page in the new tab.
- Logout from Confluence in the first browser tab (in Step 1).
- In the new browser tab, Click the search box and search for any keyword.
Expected Results
Confluence will redirect user to a Login page since the session is terminated/expired when user logout in the other tab.
Actual Results
Confluence does not redirect user to a Login page.
The following message return in the Search box when user tried to search after session timed out:
Something went wrong. Refresh the page, or contact your admin if this keeps happening.
Notes
The issue can be replicated when the default session timed out (60 minutes) without manually Logout from Confluence in other tab.
Workaround
Logout then re login into Confluence to perform the search
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-57820] Confluence Search return "Something went wrong" after session timed out instead of redirecting user to Login page.
| Description |
Original:
h3. Issue Summary
Confluence Search return "Something went wrong" after session timed out instead of redirecting user to Login page. h3. Environment Confluence version 6.14.0 h3. Steps to Reproduce # *Login* into Confluence. # Open a *new browser tab* and access any Confluence page in the new tab. # *Logout* from Confluence in the first browser tab (in *Step 1*). # In the *new browser tab*, Click the search box and search for any keyword. h3. Expected Results Confluence will redirect user to a Login page since the session is terminated/expired when user logout in the other tab. h3. Actual Results Confluence does not redirect user to a Login page. The following message return in the Search box when user tried to search after session timed out: {noformat} Something went wrong. Refresh the page, or contact your admin if this keeps happening. {noformat} h3. Notes The issue can be replicated when the default session timed out (60 minutes) without manually Logout from Confluence in other tab. h3. Workaround Logout then re login into Confluence to perform the searche |
New:
h3. Issue Summary
Confluence Search return "Something went wrong" after session timed out instead of redirecting user to Login page. h3. Environment Confluence version 6.14.0 h3. Steps to Reproduce # *Login* into Confluence. # Open a *new browser tab* and access any Confluence page in the new tab. # *Logout* from Confluence in the first browser tab (in *Step 1*). # In the *new browser tab*, Click the search box and search for any keyword. h3. Expected Results Confluence will redirect user to a Login page since the session is terminated/expired when user logout in the other tab. h3. Actual Results Confluence does not redirect user to a Login page. The following message return in the Search box when user tried to search after session timed out: {noformat} Something went wrong. Refresh the page, or contact your admin if this keeps happening. {noformat} h3. Notes The issue can be replicated when the default session timed out (60 minutes) without manually Logout from Confluence in other tab. h3. Workaround Logout then re login into Confluence to perform the search |
A fix for this issue is available to Server and Data Center customers in Confluence 6.15.2.
Upgrade now or check out the Confluence 6.15 Release Notes to see what other issues are resolved.
| Fix Version/s | Original: 6.15.1 [ 85692 ] |
| Fix Version/s | New: 6.15.2 [ 85999 ] |
| Fix Version/s | New: 6.15.1 [ 85692 ] | |
| Fix Version/s | Original: 6.15.0 [ 84699 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 412860 ] |
| QA Demo Status | Original: Not Done [ 14330 ] | New: Done [ 14331 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Awaiting Merge [ 10064 ] | New: Closed [ 6 ] |
| Status | Original: In Review [ 10051 ] | New: Awaiting Merge [ 10064 ] |
This just happened with our users on 7.4.1 Enterprise Release. Clearing cookies on the browser helped them avoid this error. So, this issues do not seem to have resolved.