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

fix: change response code to bad request for unconfigured hostname #401

Merged
merged 1 commit into from May 13, 2024

Conversation

wkillerud
Copy link
Contributor

@wkillerud wkillerud commented Apr 4, 2024

Being the internet, folks who probe the server with an invalid Host header shouldn't raise 500 error alarms in monitoring.

Being the internet, folks who probe the server with an invalid hostname
shouldn't raise 500 error alarms in monitoring.
@leftieFriele
Copy link

👍 This makes sense as having this be a 500 which for most people would their alerting systems to go off. If we return a 400 it will still be possible to monitor and pick up and invalid usages of the API.

@wkillerud wkillerud merged commit babc560 into master May 13, 2024
8 checks passed
@wkillerud wkillerud deleted the bad-request-hostname branch May 13, 2024 06:27
github-actions bot pushed a commit that referenced this pull request May 13, 2024
## [1.3.45](v1.3.44...v1.3.45) (2024-05-13)

### Bug Fixes

* change response code to bad request for unconfigured hostname ([#401](#401)) ([babc560](babc560))
Copy link

🎉 This PR is included in version 1.3.45 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants