fix(core): Respect n8n path for health endpoint#2071
Closed
everettbu wants to merge 5 commits into
Closed
Conversation
…e (#25978) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…POINT_HEALTH (#25959)
everettbu
added
n8n team
everettbu
marked this pull request as ready for review
February 23, 2026 15:05
Author
|
Upstream PR was closed or merged. Code is synced via branch mirror. |
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
4 participants
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.
Mirror of n8n-io/n8n#26129
Original author: dariacodes
Summary
In n8n-io/n8n#25729 we forgot that we have a configuration for the path, so we should respect it when constructing the health endpoint.
Related Linear tickets, Github issues, and Community forum posts
Closes ADO-4858
Review / Merge checklist
release/backport(if the PR is an urgent fix that needs to be backported)