RE: TLS termination proxy and Tapestry

2016-07-22 Thread Svein-Erik Løken
Sent: 22. juli 2016 14:52 To: Svein-Erik Løken <sv...@jacilla.no> Subject: Re: TLS termination proxy and Tapestry Forgot to mention that i also have tapestry.security-enabled= false in my app setings On Fri, Jul 22, 2016 at 3:50 PM, Dimitris Zenios wrote: > This  is a snip

Re: TLS termination proxy and Tapestry

2016-07-22 Thread Dimitris Zenios
Forwarded-Proto="https" to have request.isSecure() >> return true. >> >> Which one is the preferred method? >> >> S-E >> >> >> >> From: JumpStart [via Apache Tapestry Mailing List Archives] [mailto: >> ml-node+s1045711n5732786...@n5.nabbl

Re: TLS termination proxy and Tapestry

2016-07-22 Thread Dimitris Zenios
uot;https" to have request.isSecure() > return true. > > Which one is the preferred method? > > S-E > > > > From: JumpStart [via Apache Tapestry Mailing List Archives] [mailto: > ml-node+s1045711n5732786...@n5.nabble.com] > Sent: 22. juli 2016 13:24 > To:

RE: TLS termination proxy and Tapestry

2016-07-22 Thread Svein-Erik Løken
Start [via Apache Tapestry Mailing List Archives] [mailto:ml-node+s1045711n5732786...@n5.nabble.com] Sent: 22. juli 2016 13:24 To: Svein-Erik Løken <sv...@jacilla.no> Subject: Re: TLS termination proxy and Tapestry When you say you are avoiding absolute URLs, where have you noticed this? I c

Re: TLS termination proxy and Tapestry

2016-07-22 Thread Chris Poulsen
> > GeoLocation stopped to work I Chrome for desktop and Android, so I had > to use encryption. > > > > > > > > > > From: Chris Poulsen [via Apache Tapestry Mailing List Archives] [mailto: > ml-node+s1045711n5732784...@n5.nabble.com ml-node+s1045711n57

Re: TLS termination proxy and Tapestry

2016-07-22 Thread JumpStart
pped to work I Chrome for desktop and Android, so I had to use > encryption. > > > > > From: Chris Poulsen [via Apache Tapestry Mailing List Archives] > [mailto:ml-node+s1045711n5732784...@n5.nabble.com > <mailto:ml-node+s1045711n5732784...@n5.nabble.com>] > Se

Re: TLS termination proxy and Tapestry

2016-07-22 Thread Chris Poulsen
We are always setting tapestry.secure-enabled = false -- Chris On Fri, Jul 22, 2016 at 11:29 AM, Dimitris Zenios wrote: > When i am doing ssl out of the servlet container (eg jetty,apache etc) i > always set secure enables to false. > > On 21 Jul 2016 12:07,

Re: TLS termination proxy and Tapestry

2016-07-22 Thread Dimitris Zenios
When i am doing ssl out of the servlet container (eg jetty,apache etc) i always set secure enables to false. On 21 Jul 2016 12:07, "Svein-Erik Løken" wrote: > Using HAProxy or Apache HTTP Server as a TLS termination proxy I found > that setting X-Forwarded-Proto="https" in the

TLS termination proxy and Tapestry

2016-07-21 Thread Svein-Erik Løken
Using HAProxy or Apache HTTP Server as a TLS termination proxy I found that setting X-Forwarded-Proto="https" in the header on the proxy org.apache.tapestry5.services.Request::isSecure returns true . That's good! In tapestry.production-mode=true I am getting absolute URLs. E.g.