we have server accepts client certs means of authentication. service subsequently runs apache , terminates ssl , proxypass'es request onto our api gateway endpoint.
what we've noticed api gateway 301 redirect , our client certificate information doesn't passed along endpoint aws lambda able access.
does know if there work around this?
update 1
it seems 301 redirect caused api gateway redirecting https. problem seems if use https protocol 500 error back?
proxypass /beta/foo https://<stuff>.execute-api.eu-west-1.amazonaws.com/beta/foo proxypassreverse /beta/foo https://<stuff>.execute-api.eu-west-1.amazonaws.com/beta/foo update 2
it seem if enable sslproxyengine on , check apache error_log see of following errors:
access proxy:https://<stuff>.execute-api.eu-west-1.amazonaws.com/error/noindex.html failed, reason: ssl requirement expression not fulfilled (see ssl logfile more details) [error] (502)unknown error 502: proxy: pass request body failed <ip>:443 (<stuff>.execute-api.eu-west-1.amazonaws.com) [error] proxy: pass request body failed <ip>:443 (<stuff>.execute-api.eu-west-1.amazonaws.com) <ip> ()
Comments
Post a Comment