•  
      request #9407 HTTPS is not properly detected when behind a reverse proxy
    Infos
    #9407
    Manuel Vacelet (vaceletm)
    2016-09-02 18:12
    2016-08-18 17:18
    9684
    Details
    HTTPS is not properly detected when behind a reverse proxy

    The base structure is there but it's not used in a consistent manner in sources.

    With this patch, you should be able to run a Tuleap ran on apache in HTTP and reverse proxified by nginx without having to tweak the local.inc (except trusted_proxies of course):

    • force_ssl can be set to 1
    • https_host can have a value
    • no need to allow rest call in http

    Remember: how to setup reverse proxy: https://tuleap-documentation.readthedocs.io/en/latest/administration-guide/howto.html#deploy-tuleap-behind-a-reverse-proxy

     

    Other
    8.18
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2016-09-02
    Attachments
    References

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2016-09-02 18:12
    Got confirmation that the issue is fixed, the reopen was due to a misconfiguration.

    • Status changed from Reopen to Closed
    • Close date set to 2016-09-02
    User avatar
    Thomas Gerbet (tgerbet)2016-09-02 17:06
    In which version? I'm not able to reproduce with the current dev (8.18.99.50).
    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes