-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 1/19/17 12:21 PM, David P. Caldwell wrote:
> 1. The backend server serves files via HTTPS. (I control this, and
> may switch it to HTTP; see below.)
Ok.
> 2. The proxy server has an HTTPS connector like this (but under my
> initial
On Thu, Jan 19, 2017 at 7:15 PM, Daniel Savard wrote:
> 2017-01-19 12:21 GMT-05:00 David P. Caldwell
> :
>
>> Chris,
>>
>> Good questions, I'll try to clarify.
>>
>> 1. The backend server serves files via HTTPS. (I control this, and may
>>
2017-01-19 12:21 GMT-05:00 David P. Caldwell
:
> Chris,
>
> Good questions, I'll try to clarify.
>
> 1. The backend server serves files via HTTPS. (I control this, and may
> switch it to HTTP; see below.)
>
> 2. The proxy server has an HTTPS connector like this
Chris,
Good questions, I'll try to clarify.
1. The backend server serves files via HTTPS. (I control this, and may
switch it to HTTP; see below.)
2. The proxy server has an HTTPS connector like this (but under my
initial solution I wasn't thinking I should use it).
var _https = new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 1/19/17 10:38 AM, David P. Caldwell wrote:
> I'm trying to forward HTTPS requests through a Tomcat HTTP (or
> HTTPS) server to a backend HTTPS server.
>
> The requests are initiated by a Java HTTP client
> (java.net.URLConnection-based).
One clarification: when I wrote:
"is there something configurable that
will allow those requests to be forwarded rather than rejected?"
... what I really meant was, is there a way for the request to reach
my servlet (which handles all requests), basically. I already have a
server-side
I'm trying to forward HTTPS requests through a Tomcat HTTP (or HTTPS)
server to a backend HTTPS server.
The requests are initiated by a Java HTTP client (java.net.URLConnection-based).
So I have:
backend HTTPS server (which works)
Tomcat server running HTTP and HTTPS connectors
Java