manifoldco / manifoldco/python-manifoldco-signature
Help out Django users?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Django changes the header names like such:
... any HTTP headers in the request are converted to META keys by converting all characters to uppercase, replacing any hyphens with underscores and adding an HTTP_ prefix to the name. So, for example, a header called X-Bender would be mapped to the META key HTTP_X_BENDER.
See https://docs.djangoproject.com/en/1.7/ref/request-response/#django.http.HttpRequest.META
Options:
- Deal with it internally and maybe users can specify
django=Trueorframework='django'more broadly for future scenarios. - Allow Verifier.verify() to accept a mapping function as a param.
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
Start at the Verifier.verify() entry point and compare its expected headers with Django's request.META conversion described in the issue. Clarify which of the two proposed approaches is intended, then verify that the chosen behavior handles Django-transformed headers without changing existing verification behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100