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
When sending a message which cannot be decoded, like because of a typo in the Json message, the message fails to be processed without any error message in the log.
I was expecting some error.
After fixing the typo, my application worked as expected.
The text was updated successfully, but these errors were encountered:
Was an error sent to the client? You should get an error on the client (handled by attaching an error handler to the namespace), I'm not exactly sure how descriptive it will be though, there may be an opportunity to improve it.
Not sure what the best way to approach this is, generally a web server doesn't log parsing errors to its logs, instead it returns errors to the client because really it's the clients problem, not the servers, and the internet is full of bots and third party services throwing all sorts of junk at web servers, logging these errors doesn't usually serve any useful purpose other than creating a lot of noise in the logs.
When sending a message which cannot be decoded, like because of a typo in the Json message, the message fails to be processed without any error message in the log.
I was expecting some error.
After fixing the typo, my application worked as expected.
The text was updated successfully, but these errors were encountered: