Allow 404 error code to throw exception for declarative clients #12149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

iamsb97 wants to merge 2 commits into micronaut-projects:4.10.x from iamsb97:issue-11780

+174 −19

Contributor

iamsb97 commented Oct 21, 2025 •

edited

Loading

Addresses #11780.

Changes:

Added a new configuration property exception-on-404-status to control whether an HTTP client throws an exception or returns null when a 404 status is received.
Introduced a new interface ConfiguredHttpClient that exposes the HttpClientConfiguration associated with an individual client instance. This allows HttpClientIntroductionAdvice to access the client’s configuration in order to respect the new exception-on-404-status setting.
The default value for the new property is false, preserving existing behavior for backward compatibility.

iamsb97 added 2 commits

October 21, 2025 21:37


          Make 404 error code respect exception-on-error-status config property

49a25b8


          Introduce new configuration property exception-on-404-status

d660c0e

iamsb97 marked this pull request as ready for review

October 26, 2025 17:29

iamsb97 changed the title ~~Make 404 error code respect exception-on-error-status config property~~ Allow 404 error code to throw exception for declarative clients

Contributor Author

iamsb97 commented Oct 27, 2025

@graemerocher, please review this when you get a chance. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet