-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
"invalid internal transport message format" error message #12355
Comments
Here is where the exception comes from. As you can see we already have a best effort attempt to detect and report http traffic
This works for me:
Can you dig some more? |
This error is from 1.4.5, I can see 1.7.0 reports this response. On 21 July 2015 at 17:08, Boaz Leskes [email protected] wrote:
|
issue demystified : #10108 Closing as a duplicate then. I think it covers it well enough? |
Thanks mate. |
It'd be nice if we made this error a little more human readable -
java.io.StreamCorruptedException: invalid internal transport message format, got (47,45,54,20)
From what I understand it's due to someone talking to Elasticsearch via HTTP but to the binary API port - eg
curl localhost:9300
- so we should really just say something along those lines.The text was updated successfully, but these errors were encountered: