headers field in Remote objects report as "null" but do not accept "null"
Open
Nobody has claimed this yet.
Issue
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @mdellweg (mdellweg)
Redmine Issue: 9125, https://pulp.plan.io/issues/9125
This prevents a client to take the result from a GET call, modify it and POST it again, if it does not even know about the header field.
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
The issue concerns the headers field on Remote objects and its GET/POST round trip, but it names no file, test, or entry point. Start by locating the Remote object serialization and validation paths, then reproduce a GET followed by POST when headers is null. Done means the reported null value can be submitted back without rejection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100