Closed btrepp closed 5 years ago
If this is the kind of error I think it is, it's equally bad in the browser - so it's not because of xhr2 specifically, it's just that if an XHR request fails entirely (that is to say, there's no response at all because the URI is invalid, or the server doesn't exist, etc.) there's basically no information provided about what went wrong.
You only get meaningful errors when there is actually some response for the request.
I'd say that's exactly it. XHR is such a pain of an API. I wish it gave even a little bit more detail about what went wrong.
My root cause here is ultimately that affjax+xhr2 aren't using a http proxy, but I will raise a seperate issue about that
Is there any way to extract better errors when using with node XHR2?
Running via
pulp run
. Using attempt and purescript debug to print i getUnfortunately this doesn't give any indication as to why the request failed, which makes it hard to fix. On this machine it could be auth, proxy, or tls errrors, but I'd like to be able to see what the root cause is.
Is this a xhr2 issue? Or is it possible to get more detail from affjax?