axios: https request produce error with SSL

[VladislavAkulich]

I've got the error when I executed tests, which used this client on Jenkins environment.

Error: write EPROTO 140597680499200:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../../vendor/node/deps/openssl/openssl/ssl/s23_clnt.c:797:

at axios.then.catch (/home/jenkins/workspace/test_e2e/<project-name>/test/node_modules/reportportal-client/lib/rest.js:27:23)
at <anonymous>:null:null

It look like the following issues with axios package: axios/axios#1680

[DzmitryHumianiuk]

@VladislavAkulich are you sure assigning it to me? )

[avarabyeu]

@BorisOsipov

[BorisOsipov]

Have you tried to google smth before submiting issue?
https://stackoverflow.com/a/50781170

It works perfecly for EPAM production instance, my local setup and EPAM rp demo... So maybe issue in your server setup then?

[avarabyeu]

@BorisOsipov @DzmitryHumianiuk @VladislavAkulich
axios/axios#658 (comment)

Guys, if mentioned in issue's commit is the case, moving to axios is a big mistake and the change must be reverted.
What do you think?

[BorisOsipov]

1. restler(previous http client) doesn't support work under proxy at all see Proxy setting danwrong/restler#176 So reverting won't help
2. Issue closed with explanation "I think the problem is that the proxy you're configuring is an HTTP server, not HTTPS." So, configure you env correctly.
3. I don't care. I've already made fork for my projects to avoid dependencies from this repo

[DzmitryHumianiuk]

@VladislavAkulich resolved?

[navisayslisten]

Not resolved for me. I get this error when setting up an https url to Report Portal.

Error: Request failed with status code 404: {"timestamp":1559165140583,"status":404,"error":"Not Found","message":"No message available","path":"/api/v1/myproject/user"}
    at axios.then.catch (C:\dev\myproject\node_modules\reportportal-js-client\lib\rest.js:27:23)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)

The funny thing is, Report Portal still gets the test results. The error makes me think it didn't work at all.

[BorisOsipov]

@navisayslisten your problem aren't related to https. You ran into issue that has been fixed by b64e919