Honor zero connect and read timeouts in the Java11 client by hutiefang76 · Pull Request #3637 · OpenFeign/feign · GitHub
Skip to content

Honor zero connect and read timeouts in the Java11 client - #3637

Open
hutiefang76 wants to merge 1 commit into
OpenFeign:masterfrom
hutiefang76:frank/thirty-feign-zero-timeout-20261020
Open

hutiefang76 wants to merge 1 commit into
OpenFeign:masterfrom
hutiefang76:frank/thirty-feign-zero-timeout-20261020

Conversation

@hutiefang76

Copy link
Copy Markdown
Contributor

Closes #3635.

Honor the documented 0 = no timeout contract by omitting the JDK connect/request timeout setters for zero. An absent native connect timeout now matches zero options. Positive timeouts and rejection of negative values are preserved; streaming response-body timeouts (#3068) are outside this change.

The real HTTP baseline had 7 zero-timeout errors and 2 passing positive controls across synchronous/asynchronous execution. All 11 regression cases now pass, including negative-value controls.

Validation: root ./mvnw -Pdev validate and ./mvnw -Pdev -pl java11 -am clean verify passed with real Zulu 8/11 main compilation and Temurin 25 tests (891 tests, 0 failures/errors, 4 existing conditional skips). License and formatting checks stayed enabled.

Omit JDK timeout setters for the documented unbounded value and match a native
client with no connect timeout. Preserve positive limits and negative rejection.

Fixes OpenFeign#3635
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.

Java11 Http2Client rejects documented zero connect and read timeouts

1 participant