Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of asanso@adobe.com designates
 157.56.111.71 as permitted sender)
From: Antonio Sanso <asanso@adobe.com>
To: "dev@felix.apache.org" <dev@felix.apache.org>
Subject: Re: [FELIX-3693] HTTP SSLFilter
Thread-Topic: [FELIX-3693] HTTP SSLFilter
Thread-Index: AQHP28ME7bGMytJHvEaRIEkwptGUeZwX3YWAgAAFuIA=
Date: Mon, 29 Sep 2014 10:07:50 +0000
Message-ID: <A3FC044C-C745-47CE-BC7A-E9E76C765AED@adobe.com>
References: <034AEAB4-AB61-4974-B871-3A108FDA77C0@adobe.com>
 <9A66D44C-F3E7-427C-A91B-EB7AB48D79AE@adobe.com>
In-Reply-To: <9A66D44C-F3E7-427C-A91B-EB7AB48D79AE@adobe.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_A3FC044CC74547CEBC7AE9E76C765AEDadobecom_"
MIME-Version: 1.0

--_000_A3FC044CC74547CEBC7AE9E76C765AEDadobecom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

thanks Felix . So IIUC the logic is based on the presence of the X-Forwarde=
d-Port header right :))?

regards

antonio

On Sep 29, 2014, at 11:47 AM, Antonio Sanso <asanso@adobe.com<mailto:asanso=
@adobe.com>> wrote:

(sorry I am not subscribed to the list)

the configuration options proposed by Jan is a good solution IMHO.

regards

antonio

On Sep 29, 2014, at 10:54 AM, Antonio Sanso <asanso@adobe.com<mailto:asanso=
@adobe.com>> wrote:

hi *,

looking at [FELIX-3693] HTTP SSLFilter [0] specially at the SslFilterReques=
t it looks to me that the final Request object might end up having this wei=
rd behavior:

- request.getScheme() =3D=3D> https
- request.getServerPort() =3D=3D> 80

and possibly

- request.getRequestURL() =3D=3D> https://domain.80/active.html

IMHO having a scheme https with a port 80 might lead to some inconsistencie=
s . WDYT?

regards

antonio

[0] https://issues.apache.org/jira/browse/FELIX-4420


--_000_A3FC044CC74547CEBC7AE9E76C765AEDadobecom_--