antirez 24b3799238 redis-cli --pipe: send final ECHO in a safer way.
If the protocol read from stdin happened to contain grabage (invalid
random chars), in the previous implementation it was possible to end
with something like:

dksfjdksjflskfjl*2\r\n$4\r\nECHO....

That is invalid as the *2 should start into a new line. Now we prefix
the ECHO with a CRLF that has no effects on the server but prevents this
issues most of the times.

Of course if the offending wrong sequence is something like:

$3248772349\r\n

No one is going to save us as Redis will wait for data in the context of
a big argument, so this fix does not cover all the cases.

This partially fixes issue #681.
2013-07-03 12:02:09 +02:00
..
2012-04-13 18:05:51 -07:00
2013-01-19 11:03:19 +01:00
2013-02-11 11:44:18 +01:00
2013-01-19 11:03:19 +01:00
2013-06-27 12:14:23 +02:00
2013-06-26 15:20:56 +02:00
2013-01-19 11:03:19 +01:00
2012-10-22 11:56:06 +02:00
2013-05-14 11:22:58 +02:00
2013-01-19 11:03:19 +01:00
2013-06-26 15:21:55 +02:00
2013-04-02 14:12:28 +02:00
2013-01-19 11:03:19 +01:00
2013-01-19 11:03:19 +01:00
2013-07-02 12:24:05 +02:00
2013-07-01 10:44:08 +02:00
2013-01-19 11:03:19 +01:00
2013-01-19 11:03:19 +01:00
2013-02-05 10:49:24 +01:00
2013-07-02 12:24:08 +02:00
2013-07-02 12:24:08 +02:00
2011-07-06 15:22:00 +02:00
2013-06-26 15:26:11 +02:00
2013-07-02 12:25:30 +02:00
2013-01-19 11:03:19 +01:00