http server: fall back to base process HTTP binding if unbound path is requested #521
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.
Problem
As suggested here, it would be better for developer experience if unbound HTTP subpaths beneath a process-path (like
mynode.com/chess:distro:sys/asdf
) would default to the behavior of the base path (/chess:distro:sys/
in this case).Solution
In the HTTP server module, add a fallback if a path is not recognized that matches on the process ID and a root path (
/
) binding.We need to keep the overall behavior as-is because every path-structure (which can have URL params, etc) should be possible to configure (whether it's local-only, authenticated, etc). But for many apps, such as ones that use react router to serve 'pages', it's convenient to bind the root path once and let everything resolve to that.
Testing
Docs Update
N/A
Notes
Test this on release candidate