Anyway you can use an http load balancer more like ELB?
>From the Azure docs @ https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for Transport Layer Security (TLS) protocol termination ("SSL offload") or per-HTTP/HTTPS request, application-layer processing, review Application Gateway <https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-introduction>. If you are looking for global DNS load balancing, review Traffic Manager <https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview>. Your end-to-end scenarios might benefit from combining these solutions as needed. Max On Fri, May 4, 2018 at 10:31 AM Ejaz Ahmed <[email protected]> wrote: > Hello Everyone, > > Our superset application is hosted on Azure with a load balancer. > When accessing the application through the loadbalancer on a BYOD device, > Superset returns Bad Gateway Error. > > The application runs as expected on browsers as well as devices when on > internal network. > > The issue is not with the proxy as the application is accessible on > individual azure machines through BYOD devices. > Also, the Azure load balancer only handles TCP or UDP but 502 is a HTTP > response. > > What could be the reason for this unique scenario where superset returns > 502 on BYOD devices. > > Thanks! >
