Digest authorization header parsing bug

[kevinwatkins]

In digest.coffee, in the parseAuthorization function, the line

[name, value] = token.split "=", 2

doesn't do the right thing when the value itself might contain the character =. For example, if the request URI is

/javascript/hates?me=true

then the authorization header will contain

..., uri="/javascript/hates?me=true", ...

and the result will be to set name to uri and value to "/javascript/hates?me, truncating the URI.

[gevorg]

Thanks for reporting, fixed and published as 2.0.5 version. Gevorg