opengeospatial / opengeospatial/ogcapi-features
POST as a replacement for GET
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 386
- Forks
- 92
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 15
Description
OGC TC 05-MAR-2020: Consider using POST (e.g. aapplication/x-www-form-urlencoded) a replacement for GET in cases where the URL is too long OR we want to include private parameters for security reasons.
We don't think that this would be part of Core but perhaps another conformance class. Also, this would probably need to be bumped up to Common ... eventually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. Start by reviewing the issue's proposal about using POST when URLs are too long or parameters should remain private. Done would require deciding whether this belongs in a separate conformance class or in Common, then documenting the agreed specification change.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100