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.

I got a new install of version 7.14.1 and same problem for me; however, this Jira issue is closed.  what should we do?

Same problem on version 7.14.1

hi,

the second workaround don't work for me,

I also have another problem, when I attach a document or an image in the page in edition mode, it disconnects even if I have the option '' keep my account connected '' knowing that the cookies are deleted

Using IE version 11, I no longer have the problem of disconnection

Hi, we are in 6.2.3 and Confluence is on https. We havent received any complaints until now, hope this is fine?

Hi vellingiri.a707821256

I'd suggest opening a support ticket at https://support.atlassian.com. We can take a closer look at what's going on there.

Thanks.

Hi Team,

   I have upgraded to Confluence server 6.2.1 but still the same issue we are facing. 
   Could you please guide me in this situation?

Thanks

Hi,
It was a bug it is prevented to work in collaboration editing mode. With the update release 6.2 is the problem fixed.

That's a good explanation thanks Ze'ev, appreciated. I will upgrade to 6.1.4 (_{maybe 6.2.1}) in the coming month and report back the findings.

Hey ryan.meintjes,

This issue was resolved by filtering out Set-Cookie headers at the internal Synchrony proxy layer. So if you use the internal Synchrony proxy (which is the default from 6.1.0+ for non Data Center deployments) you will not be affected by CONFSERVER-52421.

It could be possible that CONFSERVER-52421 will affect you if you're running Confluence Data Center but it would require an unlikely network configuration. It would require at least the following:

• You're running a Data Center deployment
• Websockets is disabled on your network
• Confluence and Synchrony are accessed via the same hostname
• The load balancer or reverse proxy in front of your Synchrony cluster is configured to forward Set-Cookie headers

If you do happen to have this network configuration, I'd suggest getting it touch with support and they should be able to help out with the upgrade process and resolve any issues which arise.

Thanks, let me know if you have any follow up questions.

zgilovitz Can you reply ryan.meintjes 's question?

Hi Minh, Feng, Ze'ev

Could you comment on how this was resolved and whether the underlying cause (CONFSERVER-52421) is also resolved?

We've just moved to 6.1.3 and have near 10000 users. I've suggested to our Change Managment team that we 'apply the bugfix provided' (i.e. upgrade to 6.1.4 or 6.2.1), but they want answers to my above questions.

Thanks -ryan

A fix for this issue is now available for Confluence Server customers.
Upgrade now or check out the Release Notes to see what other issues are resolved.

A fix release - 6.1.4 - for this issue is now available for Confluence Server customers.
Upgrade now or check out the Release Notes to see what other issues are resolved.

Hi atlassianadmins,

The exact timing of our releases can change but we try to release a new version roughly every couple of weeks. This means 6.1.4 will be soon and 6.2.1 is still a couple of weeks away.

Thanks