all requests return '0 Request error' about arc-electron

[weigh2tall]

I belive I'm encountering this issue as well on 12.1.4.
I'm trying to hit a https:// public API using the GET method
I don't see any errors in the console, but receive "0 Request Error" "Requested URL can't be reached"

I just installed the 'new client'. My earlier attempt today to use the deprecated Chrome app seemed like it was working before it crashed.
Typing the same URL in Chrome does return data as expected.

[jarrodek]

@timomeara Thank you for detailed description.
It might be faster for me to debug the transport library why it reports error response without waiting for server. My email is [email protected]
Fell free to send me an example and I'll test it today.

[jarrodek]

Hey guys,
I am really sorry but it appears that the issue is my misunderstanding node's socket lifecycle.
So the HTTP client I wrote is closing the connection right after writing the message to it. Apparently some server interpret it as closing the connection and then 'close' event is send from the socket without actually checking if server has anything to say. When I've removed function that closes the connection after writing the message it finally started working (yes, I finally found an endpoint where this was happening).
I will update the app in coming hours. Thank you for very detailed descriptions and engagement.
And sorry for that issue. It never happened on any on my test endpoints..

[keycad]

@jarrodek working now with v11.0.29, thanks

[jim5359]

Working for me also. Thanks for your hard work on a great tool!

[jarrodek]

Hi,

Thank you for the issue report.
I cannot reproduce the error.
Can you provide:

1. version of the app, node and system you running the app
2. Any error message reported in the console (View > Developer > Toggle developer tools).
   That would help with tracking what is happening.

[timomeara]

sorry about not using the standard format ;) and thanks for getting back so quickly
no errors in the client
i can see that it's hitting the node app, i'm logging the request and it's being processed.
the client is failing right away.
if i put a breakpoint in the app and let a debugger stop the process the client fails even though the app has not responded.

i'm also seeing that if i keep retrying, it will eventually show a response.
(it's working maybe every 5th try)
shoot me an email and i'll share a public endpoint url

rest client version 11.0.28
system is osx 10.12.3
i'm hitting a node express app, node 6.10.0
it's a pretty basic rest API, all json responses with JWT auth
here are a few potentially relevant packages i'm using
"cors": "^2.7.1",
"express": "^4.13.3",
"jsonwebtoken": "^7.3.0",
"passport": "^0.3.2",
"passport-http": "^0.3.0",
"passport-jwt": "^2.2.1",

[jim5359]

I just installed the desktop version and I'm seeing the same problem.
http (port 80)
rest client version 11.0.28
system os: windows 10

Exact same request works fine in chrome app version.

[keycad]

I'm also experiencing the bug. I get a 400 - Bad Request error. Some information about my setup:

1. version of the app, node and system you running the app
   version 11.0.28 (it also happened with the previous version). Windows 8. Calls to localhost server (IIS) ASP.NET MVC Core Rest API

2. Any error message reported in the console (View > Developer > Toggle developer tools).
   No error:
   Processing status
   Received status 400 Bad Request
   Processing headers
   Received headers list Cache-Control: private
   Content-Type: text/html; charset=utf-8
   Server: Microsoft-IIS/8.5
   X-Powered-By: ASP.NET
   Date: Tue, 14 Nov 2017 08:39:32 GMT
   Content-Length: 4703

I've also seen that the request gets correctly to the server but then it's ARC which closes the connection (the IIS win32 error code is 10054 -"client disconnected the socket"). I can also get it to eventually work after a high number of attempts, like @timomeara said.

[jarrodek]

Thank you all for the details.
I'll try to debug it today. I'm not sure how though. Whenever I am trying to request different endpoints I can do it without problems. Today I'll be working on this.

[jaredreynolds]

This seems at least partially related to #12. @keycad mentioned localhost. Can anyone else confirm if they are having this issue with publicly available, DNS-resolved hosts? For example, https://api.github.com works fine for me.

[jim5359]

I am calling a local domain from my hosts file. So you're right, this appears to be the same issue.

I'll also add, my domain is actually a virtual machine, so it's not pointing to the local server. But the host ip address to the virtual machine is hard-coded in the hosts file on my host machine, so it seems like that may be the issue.

[timomeara]

i see the issue with both my localhost and remote instances.
both are running the exact same code, port 8080 on local, port 80 remote, same deal.
i shared a couple of my remote endpoints with @jarrodek, hopefully that will help him sort things out

[timomeara]

i've got the updae and it looks like it's working!! cheers tmo

…

On Wed, Nov 15, 2017 at 2:13 AM, keycad ***@***.***> wrote: @jarrodek <https://github.com/jarrodek> working now with v11.0.29, thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE2V_NxDfADSOETv597hp8dn1sWvsj1qks5s2p1DgaJpZM4QcaM1> .

[davidqshull]

I'm hitting this same issue in v12.1.1: works when I use the (deprecated) Chrome app, but not the macOS app.

[jarrodek]

Can you all please check if you trying to call `https` while `http` is required? That is the only thing that comes to my mind right now.

…

On Sat, Feb 17, 2018, 01:30 David Shull ***@***.***> wrote: I'm hitting this same issue in v12.1.1: works when I use the (deprecated) Chrome app, but not the macOS app. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADKo1GgNQC_iEN8T5dDPMINn90CPBVTOks5tVpwdgaJpZM4QcaM1> .

[cheahkhing]

Is this project still active? I am still facing the same issue right now. :(

[jarrodek]

It is active. Then issue has been fixed and reportes confirmed it. If you have similar issue, please report new one.