himanshug commented on pull request #11502: URL: https://github.com/apache/druid/pull/11502#issuecomment-888808462
@lokesh-lingarajan Were you actually able to dump request headers inside Druid process and verify that the 3 headers were set correctly, my guess is that `X-Forwarded-Proto` is not set to `https`. > One question - you had mentioned this setup worked for you in the past, was your druid setup on https as well ? No, Druid process was not TLS aware. From https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/using-elb-listenerconfig-quickref.html , it seems that X-Forwarded-* headers wouldn't be set if you were using the `TCP/SSL` and not the `HTTP/HTTPS` load balancer. If you have to use the TCP/SSL load balancer and consequently unable to set `X-Forwarded-*` headers then the code in this PR would be necessary. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
