Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 57A6D200C1D for ; Thu, 2 Feb 2017 07:19:56 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5645C160B5E; Thu, 2 Feb 2017 06:19:56 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9E3BC160B46 for ; Thu, 2 Feb 2017 07:19:55 +0100 (CET) Received: (qmail 45806 invoked by uid 500); 2 Feb 2017 06:19:54 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 45797 invoked by uid 99); 2 Feb 2017 06:19:54 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2017 06:19:54 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3E1CC18C37F for ; Thu, 2 Feb 2017 06:19:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id W7pne2Gb8kK6 for ; Thu, 2 Feb 2017 06:19:53 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AFCDB5FBBD for ; Thu, 2 Feb 2017 06:19:52 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CB216E039D for ; Thu, 2 Feb 2017 06:19:51 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 87D742528D for ; Thu, 2 Feb 2017 06:19:51 +0000 (UTC) Date: Thu, 2 Feb 2017 06:19:51 +0000 (UTC) From: "Vinod Kone (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MESOS-3901) Enable Mesos to be able know when it is hosted behind a proxy with a URL prefix MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 02 Feb 2017 06:19:56 -0000 [ https://issues.apache.org/jira/browse/MESOS-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849493#comment-15849493 ] Vinod Kone commented on MESOS-3901: ----------------------------------- cc [~haosdent@gmail.com] > Enable Mesos to be able know when it is hosted behind a proxy with a URL prefix > ------------------------------------------------------------------------------- > > Key: MESOS-3901 > URL: https://issues.apache.org/jira/browse/MESOS-3901 > Project: Mesos > Issue Type: Improvement > Components: webui > Reporter: Harpreet > Labels: mesosphere > > If Mesos is run behind a proxy with a URL prefix e.g. https://:/services/mesos (`/services/mesos` being the URL prefix), sandboxes in mesos don't load. This happens because when > Mesos is accessed through a proxy at https://:/services/mesos, Mesos tries to request slave state from https://:/slave/20151110-232502-218431498-5050-1234-S1/slave(1)/state.json?jsonp=angular.callbacks._4. This URL is missing the /services/mesos path prefix, so the request fails. > Fixing this by rewriting URLs in the body of every response, would not be a clean solution and can be error prone. > After searching around a bit we've learned that this is apparently a common issue with webapps, because there is no standard specification for making them aware of their base URL path. Some will allow you to specify a base path in configuration[1], others will respect an X-Forwarded-Path header if a proxy provides it[2], and others don't handle this at all. > It would be great to have explicit support in for this in Mesos. > [1] http://search.cpan.org/~bobtfish/Catalyst-TraitFor-Request-ProxyBase-0.000005/lib/Catalyst/TraitFor/Request/ProxyBase.pm > [2] https://github.com/mattkenney/feedsquish/blob/master/rupta.py#L94 -- This message was sent by Atlassian JIRA (v6.3.15#6346)