fix: Compatibility to use the storefront watcher with an non empty URI #2973
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.
1. Why is this change necessary?
My
APP_URL
looks for example like this:http://127.0.0.1/sw/platform/public
. Currently the storefront watcher fails with the message that it cannot resolve the hostname127.0.0.1/sw/platform/public
:Additionally the URL was not correctly opened, as the protocol was missing, which is fixed by this change as well.
2. What does this change do, exactly?
Parse the URL correctly in the storefront watcher script, and include an URI.
3. Describe each step to reproduce the issue or behaviour.
Start the storefront watcher using an URL like:
http://127.0.0.1/sw/platform/public
.4. Please link to the relevant issues (if any).
-
5. Checklist