Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

the max value of 'max_request_bytes' is not match

Open
#225 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start with api/src/main/proto/envoy/config/filter/http/ext_authz/v2/ext_authz.proto and trace how its uint32 max_request_bytes value is loaded from envoy.yaml into the Java xDS control plane. Reproduce the reported failure with 4294967295; done means the configuration loads that value without the current Java Int-range error.

Written by the indexing model from the issue text.

Description

We have a problem when load the file envoy.yaml to xds developing based on this project. The max value in envoy.yaml is 4294967295, but the max value in this project is 2147483647 (Java's Int type).

The content in envoy.yaml as follows:

          http_filters:
          - name: envoy.ext_authz
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.ext_authz.v3.ExtAuthz
              http_service:
                server_uri:
                  uri: 10.160.78.3:1001
                  cluster: ext-authz
                  timeout: 1s
              failure_mode_allow: false
              with_request_body:
                max_request_bytes: **4294967295**
                allow_partial_message: true

but when load the content to xds, the value exceeds the max value of Java's Int type.

[api/src/main/proto/envoy/config/filter/http/ext_authz/v2/ext_authz.proto]
uint32 max_request_bytes ;

uint32 corresponds to int in Java and int32 in Go, so this will result in an error when load the envoy.yaml.

I

Dominant language
Java
Stars
312
Forks
150
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from envoyproxy/java-control-plane

All issues in envoyproxy/java-control-plane

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.