-
Bug
-
Resolution: Fixed
-
High
-
6.1.0, 6.2.0, 6.1.2, 6.1.3
-
26
-
Severity 2 - Major
-
Environment
This bug has only been reproduced when using collaborative editing XHR fallback mode.
Symptoms
When editing a page, the user is logged out of Confluence. The user will be able to continue editing the draft but will not be able to publish it. The following flag saying "Looks like your session expired. Log in again to keep working" will be displayed.
Workarounds
1. Use Websockets for collaborative editing
This bug only affects XHR fallback mode. Confluence will use XHR fallback mode if a user cannot connect to Confluence via WebSockets.
2. Clear Cookies
This bug occurs when there is more than just the JSESSIONID Cookie stored against the Confluence domain.
- Logout from Confluence
- Remove all stored Cookies from the Confluence domain
- Login again with remember me unchecked
- Ensure no other cookies have been added by browser extensions or addons - just the "JSESSIONID" cookie should be present
- Begin editing as normal
- is caused by
-
CONFSERVER-52421 Synchrony will sometimes return Set-Cookie headers if using XHR fallback mode
-
- Closed
-
- is depended on by
-
DEVHELP-490 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Form Name |
---|
I downgraded the version to 7.13.2 and the problem is gone.
Also, when Confluence is not through a proxy on another server, it also works in version 7.14.1.
It cannot be configured to work with proxy and version 7.14.1.