Converting buffer toString() has issues with decodeURIComponent

In Parser.js headText is the encoded String of Buffer. var headText = this.buffer.toString(this.encoding, 0, headEnd);

its trying to decode decodeURIComponent('TA-Sasivarunan%ED%A0%BD%ED%B1%8D-September%E2%80%932%E2%80%932016%20%E2%80%93%201.2/Dalvik/2.1.0%20(Linux%3B%20U%3B%20Android%205.0.1%3B%20GT-I9500%20Build/LRX22C)%20(belle-sip/1.4.1)')

Actual user agent string was 'TA-Sasivarunan👍-September–2–2016 – 1.2/Dalvik/2.1.0 (Linux; U; Android 5.0.1; GT-I9500 Build/LRX22C) (belle-sip/1.4.1)'

URIError: URI malformed
    at decodeURIComponent (native)
    at /mnt/node_modules/modesl/lib/esl/Parser.js:110:44
    at Array.reduce (native)
    at Parser._parseHeaderText (/mnt/node_modules/modesl/lib/esl/Parser.js:107:28)
    at Parser._parseHeaders (/mnt/node_modules/modesl/lib/esl/Parser.js:68:25)
    at Parser._onData (/mnt/node_modules/modesl/lib/esl/Parser.js:36:21)
    at Socket.emit (events.js:107:17)
    at readableAddChunk (_stream_readable.js:163:16)
    at Socket.Readable.push (_stream_readable.js:126:10)
    at TCP.onread (net.js:540:20)

For now i’ve update the code to

Parser.prototype._parseHeaderText = function(txt) {
    return txt.split('\n').reduce(function(headers, line) {
        var data = line.split(': '),
            key = data.shift(),
            value; 
        try{
            value = decodeURIComponent(data.join(': '));
        } catch(ex){
            console.log("ERROR DECODING URI: " + ex.message + " : "  + data);
        }
        if(key === 'Content-Length') {
            headers[key] = parseInt(value, 10);
        } else {
            headers[key] = value;
        }
        return headers;
    }, {});
};

Please shed some lights on now to prevent this error.

[englercj]

@svarunan Buffer.toString() definitely does not URI encode stuff, FSW does that when it sends them over the wire. The protocol is text (utf8) and it sends items URI encoded so you can see the delimiters.

If the encoding is invalid, it is because of FSW. I would reach out to them and see if they can fix this. I had to fix their JSON encoding as well when I first made this library, so its likely this is probably fixable as well.

[englercj]

Going to close this for now since I am pretty sure this is an FSW issue, not a node-esl issue.