tursodatabase / tursodatabase/libsql
Support Remote Connection Behind HTTP Proxy?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Hey there! All of my internet access on my development machine must go through an http proxy, which is configured for most applications by setting the http_proxy and https_proxy environment variables.
I noticed that remote connections using libsql are just hanging which is usually a sign that it's not respecting the proxy, since outbound on 80 and 443 is blocked at the router.
libsql is using normal HTTP requests right? I've opened pull requests to add proxy support in a couple projects before. It's always a little different depending on which HTTP client you're using.
Do you have any pointers on where the http requests are setup and whether or not you'd be open to a fix?
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 names no files, tests, or entry points. Begin by locating where libsql remote HTTP requests are set up and checking how the http_proxy and https_proxy environment variables are handled; done means remote connections work through an HTTP proxy instead of hanging.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100