Never mind on this, sorry. I was being lazy and doing some initial
testing without using the proxy module to make sure redirects were going
to work. After I actually went to the trouble of setting up the front
end proxy and testing via it, I discovered that the proxy module does
the necessary
Ok, I have this working and have a second SSL instance on port 8443. But
I'm having an issue with redirects; when I issue a request to the
instance on port 8443 that results in a redirect, it includes the port
8443 in the URL:
curl -v -k https://server:8443/images
[...]
< HTTP/1.1 302 Found
<
Cool, thanks much for the advice. I was poking around a bit after I sent
the email and was thinking that's what I needed to do, but wasn't sure
if there was something easier.
On 3/9/2021 12:20 AM, Greg Wilkins wrote:
Paul,
You are correct that the jetty module system issetup to support only
Paul,
You are correct that the jetty module system issetup to support only a
single instance of each type of connector.
To have your setup, you will need to at least right an XML file and perhaps
a custom module to make it easy to enable.
You need to copy/paste/edit the files:
I'm going to be running an instance of jetty in AWS. I'd like it to
listen on the standard port 443 for internal https traffic, and then on
port 4443 with proxy protocol enabled behind an ELB.
I'm not clear how to accomplish that? It seems adding the proxy protocol
module just turns it on on
