[13.x] Support JSON responses for the built-in health route#59710
Merged
taylorotwell merged 3 commits into13.xfrom Apr 15, 2026
Merged
[13.x] Support JSON responses for the built-in health route#59710taylorotwell merged 3 commits into13.xfrom
taylorotwell merged 3 commits into13.xfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The framework's built-in health route always renders HTML, which is awkward for API-only applications whose load balancers, uptime monitors, and orchestrators expect JSON. Today those clients either scrape the HTML or register their own replacement route.
When the incoming request expects JSON (
$request->expectsJson()),/upnow returns:{"status": "Application is up"}or, when a
DiagnosingHealthlistener throws and debug mode is off:{"status": "Application experiencing problems"}Status codes (
200/500) are unchanged, and requests that don't expect JSON keep getting the existing Blade page.