node-red / node-red/node-red-nodes
feat(twitter): Add proxy support on twitter node.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
Currently almost all node-red supports proxy when you set the http_proxy environment variable.
Twitter node does not support it because it depends on oauth package and it does not support proxys (there are at least 5 pull requests to add proxy support to it, some of them from 2012 but none was accepted) so you cannot authenticate so you cannot work with it behind a proxy.
The message we receive points to clock, etc... It could be changed too (the error that came is ETIMEDOUT - it has nothing to do with clock)
My suggestion here is to depend only from request which already supports oauth.
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
Inspect the Twitter node's dependency on the oauth package and compare it with request's documented OAuth signing and proxy support. Reproduce the authentication failure with the http_proxy environment variable, then verify that Twitter authentication works through a proxy and that ETIMEDOUT is not reported as a clock error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100