Architecture-center: Azure Front Door doesn't support Web Sockets

Hi @mikepfeiffer Thanks for your feedback. We will review and update as appropriate.

AB#160195 - Thanks for reporting - this issue is under review

Having just tried front door and found it doesn't work with SignalR service, I'd like to +1 this. SignalR is a critical component for us (and many others), so we can't use front door at the moment.

Are there any thoughts as to when this will be included by please? It's a great product. Shame SignalR is preventing us using it.

Apart from SignalR, please list other supported protocols and technologies in the decision tree. I am particularly interested in WCF. What choices do I have when some of the clients use WCF to communicate with some of the micro services behind the gateway/load balancer?

https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq#when-should-we-deploy-an-application-gateway-behind-front-door

What protocols does Azure Front Door Service support?
Azure Front Door Service supports HTTP, HTTPS and HTTP/2.

https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-websocket
App Gateway which is a regional service supports WebSockets. Closing the issue per above pr.

@absheik , any ETA on having Web Socket Support for Azure Front Door ? https://feedback.azure.com/forums/217313-networking/suggestions/37346371-support-websocket-connections-on-azure-front-door

NO ETA?

@absheik Why is this issue closed? Does this mean that we should avoid Front Door if we have any plans to use Web sockets and instead use Application Gateway?

Please re-open since it's not fixed yet. What if you need to use Front Door in combination with Application Gateway to let the user utilize Websockets and you have an environment which is spread over multiple regions. Merging CDN into Front Door was a big deal, but when will Websockets be?