Defect #6792

Set cookie secure flag when accessing Redmine over HTTPS

Added by Sen Haerens about 11 years ago. Updated about 11 years ago.

Status:ClosedStart date:2010-11-02
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Invalid Affected version:1.0.3


Is it possible to add this to Redmine?
I'm proxying via Nginx with header "X-Forwarded-Proto https".

Full HTTPS for everything — Some sites support full encryption everywhere, but don’t implement it properly by failing to set the “Secure” flag on authentication cookies, negating most of the benefits and leaving users at risk. What that means is that any time you type the URL (e.g. “”) into your web browser (without explicitly typing https:// beforehand, which people rarely do) you will inadvertently leak your cookies with that first request, prior to being redirected to the HTTPS page. Slicehost and Dropbox are good examples of this mistake.


#1 Updated by Holger Just about 11 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

It is possible. Add :secure => true to the hash in config/initializers/session_store.rb.

In the future, please ask such questions in the forums. The issue tracker is only uses for code issues, not for support questions.

Also available in: Atom PDF