palantir / palantir/conjure-java-runtime
OkHttp retries on 413
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 96
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 33
Description
What happened?
Server sends 413 Request Entity Too Large and the client retries it the maximum number of times (4). A socket exception is then propagated to the caller.
What did you want to happen?
The client receives the 413, does not retry, and propagates the Request Entity Too Large exception.
This is an okhttp issue: https://github.com/square/okhttp/issues/1001
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing this issue alongside the linked OkHttp issue to understand the 413 retry behavior and how this runtime configures its HTTP client. Trace the relevant retry path in the repository, then verify that a 413 is returned without further retries and that the expected exception reaches the caller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100