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 #15809 Ajax calling with differente protocol
    Actions
    Infos
    #15809
    Bruno Gabrielli (bruno.gabrielli)
    2020-07-21 11:16
    2020-07-21 10:55
    17075
    Details
    Ajax calling with differente protocol
    Hello,

    In my company we're using Tuleap behind a reverse proxy and it is made available by a publisher.

    The reverse proxy receives the request on port 443 (https) and sends it to tuleap, which is running on port 80 (http).. It is the default architecture here. For the most things it is working properly, but the ajax callings does not.

    How you can in the image, the ajax callings are using http, not https. I didn't understand that. If the browser is interacting with a https server, why the callings are http? Shouldn't they be created on the client browser?
    Other
    11.15
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Waiting for information
    Empty
    Attachments
    Artifact links
    Empty
    By Bruno Gabrielli (bruno.gabrielli)
    (179 kB)
    tuleap-ajax-callings.png
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2020-07-21 11:16
    Hello,

    This is likely due to a misconfiguration and this widget is only one of the symptom.

    The reverse proxy needs to set the X-Forwarded-For and X-Forwarded-Proto headers and Tuleap needs to be properly configured to accept the information sent by the reverse proxy.

    More information here: https://docs.tuleap.org/administration-guide/system-administration/advanced-deployments.html#configure-tuleap
    • Status changed from New to Waiting for information
    • Platform cleared values: EL7 (CentOS|RHEL)
    User avatar
    Bruno Gabrielli (bruno.gabrielli)2020-07-21 10:57
    • 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