You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Obscure NullReferenceException if server does not provide a Content-Type header in polling transport #18
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.
Here is an error message from the Socket.IO connect_error handler:
Quobject.EngineIoClientDotNet.Client.EngineIOException: xhr poll error ---> System.AggregateException ---> System.NullReferenceException
в Quobject.EngineIoClientDotNet.Client.Transports.PollingXHR.XHRRequest.<Create>b__2()
в System.Threading.Tasks.Task.InnerInvoke()
в System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---
в System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
в System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
в System.Threading.Tasks.Task.Wait()
в Quobject.EngineIoClientDotNet.Client.Transports.PollingXHR.XHRRequest.Create()
--- End of inner exception stack trace ---
Not really informative, aren't they? The exact cause is provided in the first post.
Activity
mattqs commentedon Jan 23, 2016
Why is it hard to grasp?
vsoldatkin commentedon Jan 23, 2016
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.
mattqs commentedon Jan 23, 2016
OK, Reopened. Please provide a stacktrace.
vsoldatkin commentedon Jan 25, 2016
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.