e.g. if add connection to group "group++1",
Then groups in the request querystring is something like "groups=%5B%22MyHub.group++1%22%5D"
Note the special characters "++" are not encoded, so the group name actually becomes "group 1" in this case.
The special character "+" in querystring should be encoded like %2B.
This will affect the streaming transports on reconnect and long polling on every single message.
Can we see if this repros in the .NET client? Just looks like a simple case of not building the querystring correctly.
in.Net client, group names are encoded in the querystring, not repro
The .NET client rocks 😄
Can you post specific reproduction steps?
I've done the following tests to try and reproduce on my end but the + symbols are always encoded (with & without reconnect):
Aw, I just noticed that the network monitor in Chrome encodes it automatically for me, hence why I wasn't seeing it reproduced.
Changed .escape in JS source to instead be encodeURIComponent to ensu…
…re all URI componenets are encoded correctly
- Also removed an empty line in transportheartbeat
Added TransportUtilityFacts which unit test some of the transport log…
- Specifically I added a test to confirm the encoding of groups from
Cleaned up TransportUtilityFacts
- Moved a variable declaration to the top of the test
- Added semicolon after object creation
- Called "getUrl" in place instead of detaching it at the top