Closed okko closed 12 years ago
Confirmed; this appears to be an issue with the HTTP parser. ASCII characters don't seem to trigger the issue:
GET /eiloydy HTTP/1.1 HTTP/1.1 200 OK Server: Webdis Allow: GET,POST,PUT,OPTIONS Access-Control-Allow-Origin: * Content-Type: application/json ETag: "58d342ba9ffaf6fdf22bac9993e89552" Connection: Keep-Alive Content-Length: 51 {"eiloydy":[false,"ERR unknown command 'eiloydy'"]}
I'll have a look.
This is now fixed, as a side-effect of some security improvements.
This request hangs the processing. I was expecting an error reply.