1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
As it turns out, we discovered that our requests were timing out because IIS doesn't support proxy protocol. That's okay, because 2-way SSL doesn't utilize x-forwarded-for headers.
We got it to work as follows:
-
Configure the ELB to pass-through SSL to the server (Protocol = TCP, Port = 443).
-
Ensure proxy mode is disabled on the ELB (this is the default setting).
-
Configure the IIS site to accept client-side SSL certificates, using these instructions.
-
Client-Side app adds the client-cert to each rest request
-
Server-Side app's request handler inspects requests for matching client-cert thumbprint
beantwortet vor 7 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren