1. 03 7月, 2013 1 次提交
    • A
      redis-cli --pipe: send final ECHO in a safer way. · 24b37992
      antirez 提交于
      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.
      24b37992
  2. 02 7月, 2013 5 次提交
  3. 01 7月, 2013 2 次提交
  4. 27 6月, 2013 1 次提交
  5. 26 6月, 2013 21 次提交
  6. 20 6月, 2013 4 次提交
  7. 19 6月, 2013 5 次提交
  8. 04 6月, 2013 1 次提交