-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kibana crashed on ERR_UNESCAPED_CHARACTERS('Request path') #29194
Comments
Pinging @elastic/kibana-platform |
This is a regression since 6.5.4. Apparently related to our bumping node to 10. |
I used romanian characters to test this: Also, it errors out in Dev Tools as well, but it doesn't crash the Kibana server:
|
Marius used Unicode Character “ș” (U+0219) Extended ASCII (8-bit up to FF) doesn't crash it. Example: Çüéâ...Ü |
When fixed, this obviously needs an automated test added. |
Fix in the client: elastic/elasticsearch-js#756 |
Fix for Kibana #29210 |
…astic#29210) Fixes elastic#29194 In node 10, urls are validated to not include any multi-byte characters, which wouldn't be possible if we were always encoding variables injected into URLs but we missed a couple places.
…astic#29210) Fixes elastic#29194 In node 10, urls are validated to not include any multi-byte characters, which wouldn't be possible if we were always encoding variables injected into URLs but we missed a couple places.
Kibana version: 6.6.0 BC8
Elasticsearch version: 6.6.0 BC8
Server OS version: CentOS 7
Browser version: Chrome
Browser OS version: Windows 10
Original install method (e.g. download page, yum, from source, etc.): .rpm package default distribution
Describe the bug: while an automated test was creating a
makelogs-*
index pattern I was typing while the browser took focus. So the index pattern name temporarily becamemakelogs-t*
. I deleted thet
thinking the test would recover and continue. But the Kibana server process had exited.Steps to reproduce:
Expected behavior: Kibana shouldn't crash.
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
The kibana.stdout with last output at 15:39:09
The kibana.stderr which doesn't include the timestamp but stat shows modify time 1 second after the last stdout message;
Any additional context:
The text was updated successfully, but these errors were encountered: