It specifically says to avoid setting secure=true. However, that can leave you open to malicious networks stealing your JSESSIONID cookies and impersonating your session.
Why should we not set secure on the tomcat connector? Is it possible to get nginx to secure the cookie somehow instead?
The communication on the Tomcat connector (port 8090 in the example) is not secure, as it is only set up for communication between NGINX and Confluence. The client traffic is not received over that port. The proxy serves the content over SSL so the connections to the client are encrypted. The documentation you linked assumes the proxy is running on the same host as Confluence, and mentions that the NGINX>Confluence traffic is unencrypted:
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG