Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


http_proxy and https_proxy not working on domain...
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

http_proxy and https_proxy not working on domain...

jeromezajeromeza Member
edited February 2016 in General

Hi,

I'm on a Windows domain and Skype on OSX doesn't work. It bugs out with MS Forefront/Squid and locks my AD account (despite everything else working with the system wide http / https proxy in OSX).

My colleagues on Windows / Linux machines don't have this problem. I as a result have installed a Linux VM and tried to set the proxy via:

export http_proxy=http://DOMAIN\USERNAME:PASSWORD@SERVER:PORT/
export htts_proxy=http://DOMAIN\USERNAME:PASSWORD@SERVER:PORT/

BUT i'm not getting any connectivity. Is it perhaps the way Linux is trying to parse the \ after the DOMAIN name?

I've tried to use a \\ and a %5C or %40 when setting the export (noting that %5C is the encoding for a backslash and %40 is the encoding for the at sign.)

Examples:

export http_proxy=http://DOMAIN\\USERNAME:PASSWORD@SERVER:PORT/
export htts_proxy=http://DOMAIN\\USERNAME:PASSWORD@SERVER:PORT/

OR

export http_proxy=http://DOMAIN\USERNAME:PASSWORD@SERVER:PORT/
export https_proxy=http://DOMAIN\USERNAME:PASSWORD@SERVER:PORT/

OR

export http_proxy=http://USERNAME@DOMAIN:PASSWORD@SERVER:PORT/
export htts_proxy=http://USERNAME@DOMAIN:PASSWORD@SERVER:PORT/

Comments

  • I'm not clear what are you asking

    the right format http(s)_proxy :
    user:password@server:port

  • @tommy - it's a Windows domain so the format needs to be:

    domain\username:password@host:port

    Which doesn't work. Trying it with an @ and the encodings for @ and \ also don't work.

    I need to see if my formatting is correct or not...

  • jeromezajeromeza Member
    edited February 2016

    This may also have something to do with my VM being NAT'd - can't do direct as i'm on WiFi at the moment... however yum works via the proxy just fine...

Sign In or Register to comment.