-
Notifications
You must be signed in to change notification settings - Fork 74
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
Obscure NullReferenceException if server does not provide a Content-Type header in polling transport #18
Comments
Why is it hard to grasp? |
If someone uses a release build published in nuget he gets no info about the exception at all, which makes it impossible to know what exatcly went wrong and how one should fix that. Aside of that, do you by closing this issue mean you don't acknowlege this as a bug? I'm not talking about the obscurity, it is about the exception while processing the response with no header. Note that Content-Type header is optional. |
OK, Reopened. Please provide a stacktrace. |
This is what the immediate call stack looks like (via IntelliTrace):
Here is an error message from the Socket.IO connect_error handler:
Not really informative, aren't they? The exact cause is provided in the first post. |
You'll get a null reference here: https://github.com/Quobject/EngineIoClientDotNet/blob/master/Src/EngineIoClientDotNet.mono/Client/Transports/PollingXHR.cs#L328
It is accessed later in an octet-stream check producing a NullReferenceException which is quite hard to grasp using a release nuget build.
The text was updated successfully, but these errors were encountered: