feat: Implement header-based collection and geometry filtering #563
+438
−3
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.
Related Issue(s):
Description:
Adds support for filtering search results based on HTTP headers. This enables granular access control at the proxy layer while keeping sfeos authorization-agnostic.
Headers:
X-Filter-Collections: Comma-separated collection IDs to restrict accessX-Filter-Geometry: GeoJSON geometry for spatial filtering (requires optional dependencyshapely)Affected endpoints:
GET /collectionsGET /collections/{id}GET /collections/{id}/itemsGET /collections/{id}/items/{id}GET/POST /searchImportant:
There are no overhead computations if headers are not present for backwards compatibility.
PR Checklist:
pre-commit run --all-files)make test)