-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/09/14 10:59, Felix Meschberger wrote: > Hi Antonio, > > I agree this is a bug. > >> >> looking at [FELIX-3693] HTTP SSLFilter [0] specially at the >> SslFilterRequest it looks to me that the final Request object >> might end up having this weird behavior: >> >> - request.getScheme() ==> https - request.getServerPort() ==> 80 >> >> and possibly >> >> - request.getRequestURL() ==> https://domain.80/active.html >> >> IMHO having a scheme https with a port 80 might lead to some >> inconsistencies . WDYT?
I'm less inclined to immediately state this as a bug. Though it is by convention to use port 443 for secure HTTP, actually nothing prevents me from using port 80 instead for secure HTTP. - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is revolving around INAETICS and Amdatu/ Luminis Technologies B.V. Churchillplein 1 7314 BZ Apeldoorn +31 88 586 46 00 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJUKSNkAAoJEKF/mP2eHDc4A8kP/iaeXSiFyRHDK+/6i4f/Hid3 2xyX3mV2yfpMgemxEPH4ku+fR/FdCjWfwmCKGuq/JDrHxunURSECaJbx3k3LEwVo vH3otih01dyUz4hYM2AQiFjkByiFZTXS5nfkisbS8nZ/FfSGiag3h2AjlIZZd0kO 9jGI/8sgfsQKU9eqvnVr9SlNI4jQQiD5NN4I6ylemvYMoG5i3W87ykcf9RXSaStl Z3Ay2Q0moeKImlzjrm2rxaBe3/ceuQLfeRcS3y/ejLkRRb4M01WE/rQ+2zuDUCPG xhZg5OdB4UOEFNDFKMqPsnztNyIw521tLf/8e4NtZSVY3GPuoa+lQqsiIx7c/aJP VgsXZjdD9OdZvEDr+v1J35TSrUP7YV9zOC/1Iw/bKUWc4PzB3FBQlkHg/f8AHsHn 60q+mY+epN6yxWx6SO8oQk/DKMy8FRIwbamg/Ce216S47PDBQ0baduhSGQRXqfcY 8Hk/H6DjeVGNeiz77nutvh9cuYYIjANef4rGmJfSbePRNQVru+0AMIFG8TliU24r jTaBMYNwKdjdniEHSa85qyFyPMaWyS9hAEVaZkkeqmGLNEZD/ohsXHRncXS8tPFH Y9+DETgnJorK9uKxbe47ZsVu3ICNxTGExR/UpE8zC3zufZV2E2mYzFH8iukHmN+l I/6Rtaighbwm2l8et2HZ =3Iwb -----END PGP SIGNATURE-----
