tensorflow / tensorflow/tensorboard
make security_validator middleware configurable
Open
Nobody has claimed this yet.
core:backend
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
Currently, it checks whether a domain based whitelisting have https: protocol but that is sufficient. We would like it to be configurable so different application can configure it a bit differently (say only allow https://tensorflow.org based domain).
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
Locate the security_validator middleware and read how it currently enforces HTTPS for domain-based whitelisting. Determine the existing configuration and validation tests, then make the allowed protocol and domain behavior configurable and verify both the current default and a restricted example such as tensorflow.org.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100