I am not sure the reason; however, the AJAX polyfill was only pushing through the data parameter in the POST data if present. In my case, with long polling, this was leaving out messageId which seems to be fundamental in making long polling work.
This PR uses a lightweight URL parameter encoding to push the entire POST data.
This rectified the long polling functionality in my use case. I have not tested and am not aware of the following:
This may or may not fix other instances where other POST data is relied upon for correct SignalR operation.
Any regression that this my cause. I do find it peculiar that only the data parameter explicitly was being passed through so do have some concerns that this was for a valid reason.
I am not sure the reason; however, the AJAX polyfill was only pushing through the
dataparameter in the POST data if present. In my case, with long polling, this was leaving outmessageIdwhich seems to be fundamental in making long polling work.This PR uses a lightweight URL parameter encoding to push the entire POST data.
This rectified the long polling functionality in my use case. I have not tested and am not aware of the following:
dataparameter explicitly was being passed through so do have some concerns that this was for a valid reason.