tag:blogger.com,1999:blog-10712480.post6271177591658170546..comments2022-12-04T00:25:01.030+11:00Comments on Search for Simplicity: How to Update Gems from Behind a ProxyNigel Thornehttp://www.blogger.com/profile/07280667421574609074noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-10712480.post-57356964747149720382008-08-13T22:22:00.000+10:002008-08-13T22:22:00.000+10:00I had a similar problem, except my username was my...I had a similar problem, except my username was my email address, just substitute the @ for %40 (hex value of @) and it will work.<BR/><BR/>http://user%40mydomain.com:password@IP:8000Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-10712480.post-78972157494047553752008-07-09T19:26:00.000+10:002008-07-09T19:26:00.000+10:00Thanks!!!Thanks!!!alexbaumhttps://www.blogger.com/profile/16621987848593621079noreply@blogger.comtag:blogger.com,1999:blog-10712480.post-21525233372350861542008-06-17T06:58:00.000+10:002008-06-17T06:58:00.000+10:00Originally I was having his problem with a window...Originally I was having his problem with a windows/dos environment. Thanks for the feedback though.Nigel Thornehttps://www.blogger.com/profile/07280667421574609074noreply@blogger.comtag:blogger.com,1999:blog-10712480.post-79882746049881496672008-06-17T02:17:00.000+10:002008-06-17T02:17:00.000+10:00Something else you might want to consider is if yo...Something else you might want to consider is if you already have a http_proxy defined in your environment that the gem updater looks for uppercase HTTP_PROXY. So in your /etc/profile you would want to define the following:<BR/><BR/>http_proxy=http://{ipaddress}:{port}<BR/>HTTP_PROXY=http://{ipaddress}:{port}<BR/>https_proxy=http://{ipaddress}:{port}<BR/>HTTPS_PROXY=http://{ipaddress}:{port}<BR/>ftp_proxy=http://{ipaddress}:{port}<BR/>FTP_PROXY=http://{ipaddress}:{port}<BR/><BR/>export http_proxy HTTP_PROXY https_proxy HTTPS_PROXY ftp_proxy FTP_PROXY<BR/><BR/>In doing this it sets up all profiles with the proxy settings so the general users do not need to mess with their .bash_rc files in the home directories (if that is what they are using)<BR/><BR/>Im not a Linux expert, but this is what I do for my environments.<BR/><BR/>JAnonymoushttps://www.blogger.com/profile/08108222203940900242noreply@blogger.comtag:blogger.com,1999:blog-10712480.post-81296943467157144212008-04-02T19:28:00.000+11:002008-04-02T19:28:00.000+11:00You may have to html encode your username and or p...You may have to html encode your username and or password. The user name "F Bloggs" would have to be specified as "F%20Bloggs" (without the doublequoted of course.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-10712480.post-66563549963184837402008-02-07T00:08:00.000+11:002008-02-07T00:08:00.000+11:00set http_proxy=http://username:password@proxy:port...set http_proxy=http://username:password@proxy:port wouldn't work for me, because my proxy password was something like "P@ssw0rd", so yah, there you hae it. The @ sign in my password was the problem because I always used to end up with URI::InvalidURIError. Nevertheless, I called the technical guys and asked them to change my password since I can't change it myself. It works. Thanksagang sechabahttps://www.blogger.com/profile/08672540688445940562noreply@blogger.com