Re: Reverse proxy with ARR and HTTPS

2014-12-11 Thread Jesse Barnum
> On Dec 11, 2014, at 4:46 PM, Christopher Schultz > wrote: > > On 12/11/14 2:42 PM, Jesse Barnum wrote: >> I should have mentioned in my original post - IIS receives both >> HTTP as well as HTTPS requests. Both types of requests are proxied >> to a single HTTP connector in Tomcat. >> >> Is th

Re: Reverse proxy with ARR and HTTPS

2014-12-11 Thread Jesse Barnum
> On Dec 11, 2014, at 3:14 PM, Mark Thomas wrote: > >> >> Could we instead >> configure ARR to include some header that Tomcat would recognize? > > Yes. Look into the RemoteIp[Filter|Valve] Thanks Mark, I’ll look into that --Jesse Barnum, President, 360Works --

Re: Reverse proxy with ARR and HTTPS

2014-12-11 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jesse, On 12/11/14 2:42 PM, Jesse Barnum wrote: > I should have mentioned in my original post - IIS receives both > HTTP as well as HTTPS requests. Both types of requests are proxied > to a single HTTP connector in Tomcat. > > Is the only option to

Re: Reverse proxy with ARR and HTTPS

2014-12-11 Thread Mark Thomas
On 11/12/2014 19:42, Jesse Barnum wrote: > I should have mentioned in my original post - IIS receives both HTTP > as well as HTTPS requests. Both types of requests are proxied to a > single HTTP connector in Tomcat. > > Is the only option to create two separate HTTP connectors on two > different p

Re: Reverse proxy with ARR and HTTPS

2014-12-11 Thread Jesse Barnum
I should have mentioned in my original post - IIS receives both HTTP as well as HTTPS requests. Both types of requests are proxied to a single HTTP connector in Tomcat. Is the only option to create two separate HTTP connectors on two different ports, set the secure attribute to true on one of t

Re: Reverse proxy with ARR and HTTPS

2014-12-11 Thread Mark Thomas
On 11/12/2014 19:12, Jesse Barnum wrote: > I have IIS 7 running with an SSL certificate. It receives HTTPS requests, and > using ARR, it proxies them over HTTP to Tomcat. This works fine. > > The problem is that when we call HttpServletRequest.isSecure(), it returns > false. This makes sense, si