SET HTTP_PROXY= HTTPS_PROXY= used the above technique for a few weeks, untill I realized the overhead of updating my password across all the tools that needed the proxy setup. Rem looks like there is no need to URL encode stuff in there Rem as part of the value, you do not want that either Rem - if you leave a space after it, you will be including the space Rem name that includes such space, you do not want to do that Rem - if you leave a space before it, you will be declaring a variable Rem notice that there is no space before or after the = sign Rem part of the value, you do not want that Rem - I believe that if quotations are placed after it, they become Then, after (and I am reluctant to admit this) several tries (more like days), of trying to set the environment variables I finally succeeded with the following guidelines: rem notice that the value after the = has no quotations So, as the above readme explained, we can specify environment variables to set the proxy on the command line, and Request will honor those values. Turns out that even with the above configurations, I still had some issues with some packages/scripts that use Request - Simplified HTTP client internally to download stuff. WINDOWS ENVIRONMENT VARIABLES (CMD Prompt) Update Spaces and at signs are specially challenging.Do you need to encode special characters?.Is a DOMAIN string required for authentication.Weird.Įssentially you must figure out the following requirements: I used the npm config list to get the parsed values that I had set above, and that is how I found out about the double encoding. Npm config set http_proxy " config set proxy " npm config Npm config set http_proxy " config set proxy " option two (B) as of instead of URL encode it with '+', '%20 ' OR %2B (plus url encoded) please notice that I actually used a space Npm config set http_proxy config set proxy option two SoĮntering this: npm config set proxy also had to URL encode my domain\user string, however, I have a space inside my username so I put a + to encode the space URL encoding, but it would get double encoded as %2B (which is the URL encoding for the plus sign, however the URL encoding for a space is %20), so I had to instead do the following: npm command // option one The proxy configuration resulted in a forward slash appearing. My username is of the form "domain\username" - including the slash in
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |