Skip to content
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.

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

Return HTTP "404 NotFound" instead of "500 InternalServerError" when no default rule is configured and no rule matches #96

Closed
dadrus opened this issue Jul 21, 2022 · 0 comments · Fixed by #90
Labels
enhancement New feature or request
Milestone

Comments

@dadrus
Copy link
Owner

dadrus commented Jul 21, 2022

No description provided.

@dadrus dadrus added the enhancement New feature or request label Jul 21, 2022
@dadrus dadrus added this to the v0.2.0-alpha milestone Jul 21, 2022
dadrus added a commit that referenced this issue Jul 23, 2022
… code, if nor rule was applicable for the request. Related to this decision handler updated incl tests (closes #96)
@dadrus dadrus mentioned this issue Jul 23, 2022
7 tasks
dadrus added a commit that referenced this issue Jul 26, 2022
feat: New `upstream` property introduced for the rule config to support reference of the upstream service for proxy mode
feat: New management service introduced, which exposes the health & jwks endpoints
feat: Not setting HTTP Server header anymore
chore: renovate configured to always make use of semantic PRs
chore: Configuration for codecov added
fix: Fixed usage of `X-Forwarded-Uri` header
feat!: Returning HTTP 404 instead of HTTP 500 if no default rule is configured and no rule matches (#96)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant