Repository navigation
Using curl behind proxy: for nodejs#1371 - #1372
peter-lyons-kehl wants to merge 3 commits into
Conversation
|
|
||
| ***Note:*** The packages on this page are maintained and supported by their respective packagers, **not** the Node.js core team. Please report any issues you encounter to the package maintainer. If it turns out your issue is a bug in Node.js itself, the maintainer will report the issue upstream. | ||
|
|
||
| When running ```curl``` behind a proxy, invoke it as ```curl --proxy http://proxy.racp.edu.au:3128```. |
There was a problem hiding this comment.
Hmm, not sure if this change is really required, I guess people used to curling behind a proxy usually now their required config switches. Thoughts @nodejs/website?
a) Please use singleticks for inline code.
b) Maybe you should use a more generic proxy URL (something like http://<hostname>:<port> would be okay as well).
…installation (which is not obvious).
|
Hi Frederic, This will save time even for people who have used a) changed to singleticks for inline code |
|
Honestly, I see no need for this. curl honours environment variables like HTTP_PROXY, which is generally the preferred method to enable proxy usage system-wide. |
|
Personally, I agree with @silverwind, but would like to hear @nodejs/website's thoughts. |
|
I also think that the usual way is to use the |
|
Okay, I've closed this issue. But thanks for your PR, sorry it didn't work out this time. |
4 participants
No description provided.