{"issue":{"milestone":null,"title":"Adding a counter to the decoder to prevent hashflooding?","created_at":"2011-12-30T11:03:15Z","user":{"id":332898,"login":"alessioalex","url":"https://api.github.com/users/alessioalex","gravatar_id":"2c109808640f6163ce0a92810c800999","avatar_url":"https://secure.gravatar.com/avatar/2c109808640f6163ce0a92810c800999?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"labels":[],"updated_at":"2011-12-30T11:03:15Z","state":"open","id":2687939,"closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/visionmedia/node-querystring/issues/28","body":"Arnaut (`3rdEden) came up with this monkey-patch idea for the querystring native module, but I think we can implement it here also, here's what he said on the google group:\r\n\r\nThe fastest workaround for this would just be adding a counter to the decoder, and have it break out the `forEach` loop after \r\nit has stored about 1k keys in the `obj`.","number":28,"url":"https://api.github.com/repos/visionmedia/node-querystring/issues/28","comments":0,"assignee":null},"action":"opened"}