What does HTTP status 497 (Http To Https Port) mean?

HTTP_STATUS_HTTP_TO_HTTPS_PORT

The client connected to a TLS port but sent an unencrypted HTTP request. NGINX parses enough of the request to make the URI available for an error_page redirect or error response.

Use an https:// URL and verify port mappings in reverse proxies, health checks, and service discovery. Do not try to fix this by changing HTTP headers after the connection is opened.

NGINX SSL module

Operational meaning of HTTP 497 for HTTP_STATUS_HTTP_TO_HTTPS_PORT

HTTP 497 (HTTP_STATUS_HTTP_TO_HTTPS_PORT) is a client-error response. AllStat records its meaning as “497 HTTP Request Sent to HTTPS Port”. For HTTP_STATUS_HTTP_TO_HTTPS_PORT, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.

Client and server handling for HTTP_STATUS_HTTP_TO_HTTPS_PORT

• Treat HTTP_STATUS_HTTP_TO_HTTPS_PORT as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
• For HTTP_STATUS_HTTP_TO_HTTPS_PORT, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
• For HTTP_STATUS_HTTP_TO_HTTPS_PORT, automatic retry is safe only when the method and status contract allow it and the request has been corrected.

For telemetry, record HTTP 497, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.

Looking for a different code? Search another status or error code.