Skip to content
If you are interested in trying out Gloo Gateway with the Kubernetes Gateway API, check out Solo Enterprise for kgateway. This version adds enterprise functionality on top of the kgateway open source project.

Requests

Page as Markdown

Troubleshoot connectivity issues for your requests.

HTTP request sent to HTTPS port

What’s happening

When you send a request to a backing destination through Gloo Gateway, you get a 400 Bad Request response with a message similar to the following.

The plain HTTP request was sent to HTTPS port

Why it’s happening

You have a basic example with an HTTP listener on the gateway. However, you also have an Istio integration that enables mTLS, which sends the HTTP traffic to the HTTPS port.

In your Helm installation, you might have the following settings:


global:
  istioIntegration:
    enableAutoMtls: true
    enabled: true

How to fix it

Choose from the following options: