Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #9407 HTTPS is not properly detected when behind a reverse proxy
    Actions
    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
    By Matthieu Monnier (mmonnier)
    (64 kB)
    tuleap_csrf_kanban.png
    By Matthieu Monnier (mmonnier)
    (74 kB)
    tuleap_csrf_scrum.png
    References
    Referencing request #9407

    Artifact Tracker v5

    request #9467 Fatal error when connecting to soap tracker client

    Git commit

    tuleap/tuleap/stable

    Merge 'gerrit #6362' into stable/master bd23449266
    User avatar Thomas Gerbet (tgerbet) , 2016-08-24 11:42
    request #9407 HTTPS is not properly detected when behind a reverse proxy 0c529cf27b
    User avatar Manuel Vacelet (vaceletm) , 2016-08-24 09:57
    Referenced by request #9407

    Artifact Tracker v5

    rel #9211 8.18
    rel #9212 8.19

    Other

    gerrit #6362
    Display settings

    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
    Manuel Vacelet (vaceletm)2016-08-18 17:26
    • 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