Fix tenant identification in assets when using path-identification #1121
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.
By default, calling
tenant_asset()
results in an asset URL like '/tenancy/assets/{path}`. This works fine for everything except path-identification since the tenant_id is required to be in the path itself.These fixes add a second parameter to
tenant_asset(string $path, bool $usePathIdentification = false)
which uses a different route to enable proper URLs can be generated.This restored functionality required a few other tweaks and some extra protection against path traversal attacks.