Add support for serving well-known URIs with the @astrojs/node SSR adapter #5832
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.
Changes
This PR fixes #5813.
Well-Known locations, e.g.
/.well-known/apple-app-site-association
are properly served when runningastro dev
altho this is not the case for a production build served using the@astrojs/node
SSR adapter.This PR introduced changes discussed in #5813 and suggestions from @bluwy to properly serve well-known URIs (a URI whose path component begins with the characters
"/.well-known/"
). This is achieved with 2 changes:public
directory, dotfiles are now also copied over.@astrojs/node
adapter no longerdeny
dotfiles for well-known URIs.Testing
astro
test forstatic-build
to ensure dotfiles from thepublic
directory are copied over during an SSR build.@astrojs/node
tests in awell-known-locations
suite to ensure well-known URIs are properly served while other dotfiles are not.Docs
I couldn't find any mention of the current behavior in the documentation so I'm not sure if any changes are needed.
/cc @withastro/maintainers-docs for feedback!