You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: fix returned value for max_headers_count. It was 503 now it is 502. (#40006)
Tested and the actual returned code differs from docs:
```http
❯ curl https://httpbin.example.com/policy/response-headers -ki
HTTP/1.1 502 Bad Gateway
content-length: 87
content-type: text/plain
date: Mon, 23 Jun 2025 17:08:56 GMT
server: envoy
upstream connect error or disconnect/reset before headers. reset reason: protocol error%
```
<!--
!!!ATTENTION!!!
If you are fixing *any* crash or *any* potential security issue, *do
not*
open a pull request in this repo. Please report the issue via emailing
[email protected] where the issue will be triaged
appropriately.
Thank you in advance for helping to keep Envoy secure.
!!!ATTENTION!!!
For an explanation of how to fill out the fields, please see the
relevant section
in
[PULL_REQUESTS.md](https://github.com/envoyproxy/envoy/blob/main/PULL_REQUESTS.md)
-->
Commit Message: fix returned value for ``max_headers_count``. It was 503
now it is 502.
Additional Description:
Risk Level: Low
Testing:
Docs Changes:
https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#envoy-v3-api-msg-config-core-v3-httpprotocoloptions
Release Notes: fix returned value for ``max_headers_count``. It was 503
now it is 502.
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional [API
Considerations](https://github.com/envoyproxy/envoy/blob/main/api/review_checklist.md):]
---------
Signed-off-by: Jesus Munoz <[email protected]>
Mirrored from https://github.com/envoyproxy/envoy @ 427f3d9aaaebee42c97222a1e75214baeb67723f
0 commit comments