Skip to content

Enable http1.0 on Envoy Gateway by default#812

Open
theboringstuff wants to merge 1 commit into
mainfrom
fix/envoy-http1.0
Open

Enable http1.0 on Envoy Gateway by default#812
theboringstuff wants to merge 1 commit into
mainfrom
fix/envoy-http1.0

Conversation

@theboringstuff
Copy link
Copy Markdown
Collaborator

@theboringstuff theboringstuff commented May 25, 2026

Description

There are clients which are using http1.0, so to be better compatible with ingress-nginx, we need to enable http1.0 support in envoy gateway

Solution

  • Enabled http1.0 support by default

Test Cases

  1. Install KubeMarine cluster with Envoy Gateway
  2. Check that HTTP 1.0 requests DO NOT return 426 status code, see example below (put your ENVOY_IP and ENVOY_HTTPS_PORT)

Before (note first requests return 426, while others return 404)

$ curl -s -o /dev/null -w "%{http_code}\n" -k https://$ENVOY_IP:$ENVOY_HTTPS_PORT --http1.0
426
$ curl -s -o /dev/null -w "%{http_code}\n" -k https://$ENVOY_IP:$ENVOY_HTTPS_PORT --http1.1
404
$ curl -s -o /dev/null -w "%{http_code}\n" -k https://$ENVOY_IP:$ENVOY_HTTPS_PORT --http2
404

After (note all requests now return 404)

$ curl -s -o /dev/null -w "%{http_code}\n" -k https://$ENVOY_IP:$ENVOY_HTTPS_PORT --http1.0
404
$ curl -s -o /dev/null -w "%{http_code}\n" -k https://$ENVOY_IP:$ENVOY_HTTPS_PORT --http1.1
404
$ curl -s -o /dev/null -w "%{http_code}\n" -k https://$ENVOY_IP:$ENVOY_HTTPS_PORT --http2
404

Checklist

  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • There is no breaking changes, or migration patch is provided
  • Integration CI passed
  • Unit tests. If Yes list of new/changed tests with brief description
  • There is no merge conflicts

@theboringstuff theboringstuff changed the title enable http1.0 by default Enable http1.0 on Envoy Gateway by default May 26, 2026
@theboringstuff theboringstuff marked this pull request as ready for review May 26, 2026 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants