temporalio / temporalio/temporal
Allow auth headers to be sent to HTTP on localhost
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When developing a codec server, it's always frustrating to have to run my localhost version through ngrok to get an HTTPS address. Many OAuth providers (eg, GitHub) have an exception that allow localhost to be run on HTTP.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Allow http://localhost
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Use ngrok
Additional context
Add any other context or screenshots about the feature request here.
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 file, test, or entry point is named. Start by locating the code and tests that decide whether authentication headers may be sent to an HTTP origin, then verify the requested behavior for http://localhost and its effect on other origins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100