fix flatgeobuf params by getRequestConfigurationByUrl#12200
Merged
allyoucanmap merged 1 commit intogeosolutions-it:masterfrom Mar 31, 2026
Conversation
1 task
allyoucanmap
approved these changes
Mar 31, 2026
Contributor
|
@ElenaGallo please test this fix on dev, thanks |
Member
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-12200-to-2026.01.xx
git worktree add --checkout .worktree/backport-12200-to-2026.01.xx backport-12200-to-2026.01.xx
cd .worktree/backport-12200-to-2026.01.xx
git reset --hard HEAD^
git cherry-pick -x 06c0454619cb2ead15ce8d7e6800ca9fd25f3545
git push --force-with-lease |
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
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.
Fix #12162
Description
In short, in cases of datasets using custom rules in the requestsConfigurationRules section of localConfig.json, the URL parameters for resource addresses corresponding to COG and FlatGeobuf files were not being passed. See the issue for an example of rules to use for testing.
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#12162
What is the new behavior?
Ensure the security params are included inside FlatGeoBufLayer in openlayers
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
See the linked issue for bug reproducing details.
Geonode-client porting is required