Make the path of web endpoints configurable
See original GitHub issueMany gateways and load balancers ping a URL and just need a 200 back to consider a server to be a candidate for handling requests. We’ve also heard of teams that “require” this URL to be /health
. Given that all they need is a 200 response, the status endpoint is currently the best fit but it’s mapped to /status
. We should consider making /health
provide the rolled up information about the health of the application and making /status
provide detailed information.
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Configure endpoints for the ASP.NET Core Kestrel web server
Learn about configuring endpoints with Kestrel, the cross-platform web server for ASP.NET Core.
Read more >51. Endpoints - Spring
51.8.2 Custom Web Endpoints · Web Endpoint Request Predicates · Path · HTTP method · Consumes · Produces · Web Endpoint Response Status...
Read more >Step 2: Endpoints and methods (API reference tutorial)
The endpoints indicate how you access the resource, while the method indicates the allowed interactions (such as GET, POST, or DELETE) with ...
Read more >Authorization of Web Endpoints - Quarkus
root-path configuration property is used to change the http endpoint context path. By default, quarkus.http.root-path is prepended automatically to configured ...
Read more >Website endpoints - Amazon Simple Storage Service
Configure an Amazon S3 bucket for website hosting to make it available through the AWS Region-specific website endpoint.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Reconsider swapping them. The naming is right now IMO so I’d really like to keep things as they are now.
If we want to do that, we have no choice IMO,
status
should go away and should be renamed to something that states it provides additional details. It is a shame because I think the current names are just about right (I am not a huge fan of/healthdetails
and anHealhDetailsEndpoint
), this constraint of having the existing endpoint showing only the status is messing things up 😦Can we reconsider perhaps? We want to use 2.0 to fix things and I believe this is one of them.