Add sane error message for unreachable host
See original GitHub issuenajax: method jqXHR.“getAllResponseHeaders” not implemented
Update
I’m observing the following error every time my fastboot ember app goes to a route with this.store.query()
:
najax: method jqXHR."getAllResponseHeaders" not implemented
[object Object]
at Object.getAllResponseHeaders (/www/node_modules/najax/lib/najax.js:108:15)
at ajaxResponseData (/www/tmp/broccoli_merge_trees-output_path-xxExqEhS.tmp/assets/addon-tree-output/ember-data/adapters/rest.js:1116:1)
at ajaxErrorHandler (/www/tmp/broccoli_merge_trees-output_path-xxExqEhS.tmp/assets/addon-tree-output/ember-data/adapters/rest.js:1106:1)
at Object.hash.error (/www/tmp/broccoli_merge_trees-output_path-xxExqEhS.tmp/assets/addon-tree-output/ember-data/adapters/rest.js:877:1)
at fire (/www/node_modules/jquery-deferred/lib/jquery-callbacks.js:78:30)
at Object.fireWith (/www/node_modules/jquery-deferred/lib/jquery-callbacks.js:188:7)
at Object.fire [as reject] (/www/node_modules/jquery-deferred/lib/jquery-callbacks.js:195:10)
at ClientRequest.onError (/www/node_modules/najax/lib/najax.js:208:9)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
On routes with multiple queries, I’m observing this message many times. It is flooding my logs.
The routes seem to work because Fastboot returns a non-fastboot page, which works.
This happens when the domain can be reached from the client, but cannot be reached from the Fastboot server.
Please add a more sane error message, as this makes it seem like the response is fine but something is wrong with the najax
library.
Looks like this issue:
@kedano commented on Mar 3, 2016:
ember serve
works just fine on the project and it looks likeember fastboot
almost works as well except for one issue:
najax: method jqXHR."getAllResponseHeaders" not implemented
Except that issue was fixed five hundred two years ago. The current issue has a different cause.
$ cat node_modules/ember-cli-fastboot/package.json | grep \"version\":
"version": "1.1.4-beta.1"
$ ./node_modules/.bin/ember version --verbose
ember-cli: 3.3.0
http_parser: 2.8.0
node: 8.12.0
v8: 6.2.414.66
uv: 1.19.2
zlib: 1.2.11
ares: 1.10.1-DEV
modules: 57
nghttp2: 1.32.0
napi: 3
openssl: 1.0.2p
icu: 60.1
unicode: 10.0
cldr: 32.0
tz: 2017c
os: linux x64
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6
Top GitHub Comments
I started getting the same error not so long ago. It happens on my VM, but not when I run it straight from my wsl console locally.
Internally, there’s a
getaddrinfo EAI_AGAIN error
that results in agetAllResponseHeaders
call that fails. For me at least, it was caused by running on a VM that was named in my host-machine’s host-file, but not internally in the VM itself. So adding this line to the VM’s/etc/hosts
file resolved the issue:I’ve run into the same problem because after 6 months apparently I forget things. 😅 I could have wasted less time if the actual problem would have a sane error message.
Most of the nAjax stuff was written by @danmcclain over 3 years ago. Any thoughts on this issue?