Support for Legacy Clients Connecting to a service in Azure with HTTP 1.0

Question

Hi there,

We have a service that runs in Azure Web App Service. This application currently supports client requests using HTTP 1.0. However, legacy HTTP 1.0 curl requests receive a 426: upgrade required when routing to an Azure Container App.

It's clear from the documentation that Azure Container App's ingress only supports HTTP 1.1/2.0. Additionally when deploying the containerized application through a new App Service instance we see that HTTP 1.0 is not supported.

What does the community suggest to support the HTTP 1.0 client if upgrading their application is not an option? (App Gateway?). Are there release notes on when this protocol stopped being supported? I know ingress Nginx upgrade 1.0 requests to 1.1 for normal k8s clusters.

Thank you!

Answer 1

@Hunter

Thank you for reaching out.

I understand you wish to know about support for clients connecting to a service in Azure with HTTP 1.0 legacy protocol.

Based on your question above.

What does the community suggest to support the HTTP 1.0 client if upgrading their application is not an option? (App Gateway?).Azure Application Gateway can accept HTTP/1.0 traffic (ingress traffic from client) but the backend communication (Between Application Gateway and the backend server) has to be HTTP/1.1.

This is currently documented here

Hope this helps! Please let me know if you have any additional questions here. Thank you!