https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292017-01-19T15:52:04ZRedmineRedmine - Defect #24880: Documentation for enabling HTTPS is not clearhttps://www.redmine.org/issues/24880?journal_id=761352017-01-19T15:52:04ZToshi MARUYAMA
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Redmine is Rails app and does not depend any Webserver (Apache, Thin, Puma etc.).<br />So there is no way to document it.</p> Redmine - Defect #24880: Documentation for enabling HTTPS is not clearhttps://www.redmine.org/issues/24880?journal_id=761362017-01-19T15:54:34ZJonathan Schneider
<ul></ul><p>So it's a Rails problem ?</p> Redmine - Defect #24880: Documentation for enabling HTTPS is not clearhttps://www.redmine.org/issues/24880?journal_id=761372017-01-19T15:58:50ZToshi MARUYAMA
<ul><li><strong>Resolution</strong> set to <i>Wont fix</i></li></ul><p><a class="external" href="https://www.google.com/search?q=rails+apache+https">https://www.google.com/search?q=rails+apache+https</a></p> Redmine - Defect #24880: Documentation for enabling HTTPS is not clearhttps://www.redmine.org/issues/24880?journal_id=762572017-01-24T16:40:41ZCheyenne Wills
<ul></ul><p>It appears that Ruby Rails 4 is more picky on the headers now. We had:<br /><pre>
RequestHeader set X_FORWARDED_PROTO "https"
</pre><br />in our proxy apache config. This needed to be changed to <br /><pre>
RequestHeader set X-Forwarded-Proto "https"
</pre></p>
<p>We also had a utility that was using the rest api break because there was a small error in one of the headers that started to get a 400 invalid header response.</p> Redmine - Defect #24880: Documentation for enabling HTTPS is not clearhttps://www.redmine.org/issues/24880?journal_id=779632017-04-11T16:37:46ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" href="/issues/25577">Defect #25577</a>: Fixing wrong hyphenization on FAQ-Page for RequestHeader</i> added</li></ul>