Closed davidfowl closed 11 years ago
Is there any additional info in the logs? I'm unable to repro this and after spending a significant amount of time in the JS source I feel as though this was the result of someone messing around with their client.
The &groups=val addition to the query string is ALWAYS an array via @halter73 addition of the getGroups method:
getGroups: function (connection) {
var groups = [];
if (connection.groups) {
$.each(connection.groups, function (group, _) {
// Add keys from connection.groups without the # prefix
groups.push(group.substr(1));
});
}
return groups;
}
This is called prior to appending the data to the query string.
In addition to this the messageId field in the request is funky. After clarifying its format with @halter73 it should not be possible for there to be a colon in the message id. Which is why i'm leaning towards this being a false alarm.
For now I'll assign this to @Xiaohongt for reproduction when time permits.
There's nothing else there. It could be a browser specific thing but it does happen. I'm sure it's not somebody messing with the client.
Seems like it's this nodejs client https://github.com/smoak/njabbr/blob/master/lib/transports/common.js#L174
Found this in the jabbr.net logs. It seems for some reason groups are being sent as a json object instead of an array in some cases.