Axios: Request to HTTPS with HTTP proxy fails

[kparkov]

Summary

Trying to do a HTTPS request with a HTTP proxy fails.

const req = await axios({
  url: 'https://somedomain.com',
  proxy: {
    host: '89.151.146.7',
    port: 6060,
    auth: {
      username: 'myname',
      password: 'mypass',
    },
  },
});

Results in:

Error: write EPROTO 140736379442112:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:794

The problem is already described by @chovy in this ticket, which ended up closed as OP did not have the same problem: https://github.com/mzabriskie/axios/issues/662

@chovy says:

I still have this issue not being able to hit an https url with an http proxy. I can do it fine in request and also in curl from shell. Something not working with axios. I get an EPROTO error.

 Context

• axios version: v0.16.1
• Environment: node v7.10.0, Mac OSX Sierra

[gigachel]

I'm having the same problem of https request over proxy. I do not want to move to request.js.

return axios({ url: 'https://site.com', proxy: { host: 'proxy.xxxxxx.com', port: 3128 } })
Result:
Error: write EPROTO 139800246822688:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:794

request.js and curl in this situation works well.

Context

• axios version: v0.16.1
• Environment: node v6.9.5, CentOS release 6.8 (Final)

[Khaledgarbaya]

Me and a colleague of mine identified the problem, a PR should be coming soon

[Khaledgarbaya]

the PR is here https://github.com/mzabriskie/axios/pull/959

[mpcen]

Same issue here: Requesting https resources behind an http proxy.

axios.get('https://resources.json', {   
   proxy: {
      host: 'http://my.proxy.com',
      port: 12345
   }
})
   .then(() => {})
   .catch(() => {});

Result:
Error: getaddrinfo ENOTFOUND http://my.proxy.com http://my.proxy.com:12345

[kunokdev]

Any progress on this so far?

[Meg4mi]

Same problem here.

Any news ?

[kunokdev]

My problem was not related to proxies tho, I had to send GET request to https domain which wasn't certified. In curl inside linux terminal, solution was to use -k or --insecure flag. I couldn't find Axios solution tho, but with request lib I done it like so; might give you idea:

const agentOptions = {
    host: '10.100.0.10',
    port: '443',
    path: '/',
    rejectUnauthorized: false,
  }

const agent = new https.Agent(agentOptions)
request({
      url: 'https://10.100.0.10/myUncertifiedTargetUrl',
      method: 'GET',
      agent,
    }, (err, resp, body) => {
...

[mistermoe]

Feel free to use this until they get #959 merged.

[PedramMarandi]

Same here, btw @mistermoe's PR works fine

[sneko]

@mistermoe I just left work without making it succeeded :(

I use this package : https://github.com/Yoctol/messaging-apis/tree/master/packages/messaging-api-messenger

And if I replace "axios" by yours, the following error disappears:
"Error: write EPROTO 139800246822688:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:794"

But I have something like:
"Error: getaddrinfo EAI_AGAIN"

I notice that the Messenger plugin makes requests like that:
`
let client = axios.create({ ... });

client.get('...')
`

Did you succeed by this way or not directly by Axios "request" function?

Thanks!

EDIT: Another one having this issue:
https://github.com/axios/axios/pull/959#issuecomment-337595602

[cur3n4]

Any chance of merging this? Could we leverage the newly added config.transport to avoid this issue?

[skuarch]

ups, same problem here!

[Sitronik]

Unfortunately, this pull request doesn't merged, but I fixed this issue https://github.com/Sitronik/axios

[jan-molak]

Had a similar issue recently, my solution was to use an HTTPS-over-HTTP tunnel, specify port 443 explicitly in the URL and disable automatic proxy detection in axios:

import axios, { AxiosInstance } from 'axios';
import * as tunnel from 'tunnel';

const tunnel = tunnel.httpsOverHttp({
    proxy: {
        host: 'proxy.mycorp.com',
        port: 8000,
    },
});

const httpClient: AxiosInstance = axios.create({
    baseURL: 'https://some.api.com:443',
    httpsAgent: tunnel,
    proxy: false,
});

More about the solution in this article.

Hope this helps,
Jan

[Sitronik]

@jan-molak My fix is easy to use:

1. npm install axios-https-proxy-fix
2. Then

import axios from 'axios-https-proxy-fix'; 

const proxy = {
  host: 'some_ip',
  port: some_port_number,
  auth: {
    username: 'some_login',
    password: 'some_pass'
  }
};

async someMethod() {
  const result = await axios.get('some_https_link', {proxy});
}

[b4hand]

@jan-molak's solution worked for me as well. It would really be nice to not have to force the port number on the url though.

[Alexis374]

@jan-molak @Sitronik I tried your solution but get Error: socket hang up.
What I want is see how the request go through charles,so I open charles,and set proxy to {host:'127.0.0.1',port:8888} in my code. I don't know whether it is suitable to use your solution

[astappiev]

Any chance to be included in 0.19.0?

[emilyemorehouse]

@astappev this definitely looks like it needs a fix ASAP. There's a lot of related issues and PRs that I need to sift through, but I'll add it to my 0.19.0 roadmap.

[astappiev]

@emilyemorehouse, do you have any estimation when it will be released?
The PR #959 solve critical part of the issue, other issues like proxying redirections and so can be improved later. The changes in #959 are pretty simple and can be published in just few minutes.

[anhnt]

@Sitronik that works for me thanks

[necevil]

@jan-molak 's fix saved my day.
+1 to merging the PR.

[SrWildman]

Another +1 to merging this!!

[prokopsimek]

Same issue... please merge!

[raphaelsoul]

Same issue here

[camueller]

@Sitronik that works for me thanks - please merge!
However the proxy settings does not seem to be read from environment variables (http_proxy / https_proxy) but have to be specified as part of AxiosRequestConfig.

[necevil]

+1 Still using work arounds mentioned above but would love to see this work out of the box.

[fractalzombie]

+1 When you fix this? But we need no_proxy too...

[Makoehle]

@Sitronik please add PR. Your package axios-https-proxy-fix works just fine. axios.defaults.proxy = {host: ip, port: port}

[m2jobe]

Still an issue, would use that package but its many commits behind? Would that be a non issue :S

[Makoehle]

would use that package but its many commits behind?

Same for me while waiting for that change I'm going for node-fetch + httpsProxyAgent + bluebird. Works fine.

[m2jobe]

@Makoehle

Hey I ended up getting it to work, try export http and https to "" on your terminal

export http_proxy="" && export https_proxy=""

[Makoehle]

Thank you I know about env variables. I tried everything. My guess is it has to do with #1207

[lderzhavets]

Waiting for merge too. Why it is so long?

[emilyemorehouse]

959 was merged and is available in 0.19.0-beta.1

[czl032405]

I can not solve it out in 0.19.0-beta.1, but I fixed like this

// default axios usage
import * as ProxyAgent from "proxy-agent";
const proxyAgent = new ProxyAgent(process.env.HTTPS_PROXY);  // http://127.0.0.1:1080
Axios.defaults.httpsAgent = proxyAgent;
Axios.defaults.proxy = false;

// google api usage
const Sheets = google.sheets({
    version: "v4",
    auth: key,
    httpsAgent: /dev/.test(process.env.NODE_ENV) ? proxyAgent : false,
    proxy: false
});

[Khaledgarbaya]

0.19.0-beta.1 should fix the issue, I am closing the issue and feel free to create a new one if anyone still having the issue

[necevil]

@Khaledgarbaya I am still having this issue with 0.19.0-beta.1
My question is what should my proxy request look like (and how does the isHttps flag work?).

I assumed that for HTTPS over HTTP I would simple set the http url / port for the proxy like this:

axiosRequestOptions.proxy = {
            host: '192.0.01',
            port: '8888',
            // isHttps: true, ?
        }

That being said the above still fails so I am wondering if it is a configuration / documentation issue where my structuring of the proxy property / object is the cause.

[Sitronik]

@necevil
host: '192.0.01'

[bidhan-a]

The 0.19.0-beta.1 still does not work. I kept getting Request failed with status code 400. Wasted a lot of time on this. Switched to the request library and it worked like a charm on the first try.

[mikkqu]

Ran into the same problem.

const axios = require('axios-https-proxy-fix')

fixed the problem for me.

[mrodrig]

After updating to 0.18.0 this seems to be working for me. I had to specify the following options for my use case though:

axios.get('<some_url_on_corporate_intranet>', {
        proxy: false,
        httpsAgent: https.Agent({
            rejectUnauthorized: false // Allows the use of self-signed certificates (not recommended)
    })

[redbearder]

tried all solution and all failed base on axios 0.18
final solution :
install nginx module ngx_http_proxy_connect_module
then request https url via http proxy with request-promise

[chovy]

You don’t need Nginx if you’re using request. Request handled proxies fine.

-
Anthony

On Jan 17, 2019, at 8:44 PM, redbearder [e-mail] wrote:

tried all solution and all failed base on axios 0.18
final solution :
install nginx module ngx_http_proxy_connect_module
then request https url via http proxy with request-promise

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[redbearder]

You don’t need Nginx if you’re using request. Request handled proxies fine. - Anthony
…
On Jan 17, 2019, at 8:44 PM, redbearder @.*> wrote: tried all solution and all failed base on axios 0.18 final solution : install nginx module ngx_http_proxy_connect_module then request https url via http proxy with request-promise — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Thank you for reply
I assume that people will send requests via single IP address as proxy gateway, that is what I will do
However request-promise catch a error "RequestError: Error: tunneling socket could not be established, code 400"
so I dont find solution from Node and then I try to fix it from Gateway side
and the solution comes out above

[YassienW]

2 years later, still broken!!!

[chovy]

Use request promise.

Anthony
http://profullstack.com

On Jul 18, 2019, at 7:05 AM, Yassien [e-mail] wrote:

2 years later, still broken!!!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[YassienW]

Here's what i did for those who stumble upon this and still want to use axios:

const HttpsProxyAgent = require("https-proxy-agent"),
      axios = require("axios");

const httpsAgent = new HttpsProxyAgent({host: "proxyhost", port: "proxyport", auth: "username:password"})

//use axios as you normally would, but specify httpsAgent in the config
axios = axios.create({httpsAgent});

This will let you make https requests over an http proxy, simple and neat.

[pittersnider]

Still having the same issue after 2 years.
Is someone working on this or can we join to contribute?

[klibs]

Just ran into this issue myself. Hoping you guys can fix this at some point.
czl032405's solution of using proxy-agent worked for me.

[YassienW]

According to the 0.19.0 release, this has been fixed. Since it obviously hasn't, a new issue should be opened

[axiac]

This functionality is still broken in axios 0.19.
Version 0.19.0 fails with the message _"Error: Protocol "http:" not supported. Expected "https:""_
Version 0.19.1 fails with _"Error: timeout of 1000ms exceeded"_. Increasing the timeout doesn't help. The proxy server expects a CONNECT request while axios sends a GET request.