Re: Help with 400 Bad Request

Joe Martinez wrote:

> Actually, while I was waiting, I found that same SO question, and
> implemented that workaround.  I just sent another request, using the
> workaround.  This time, I got "Authorization required." in the body.  Can
> you check that one?

This was the old header:

>> Authorization: Digest  
>> username="jmartine",realm="musicbrainz.org",nonce="9SeEag2TSsSWn5OpDa/C0Q==",uri="/ws/2/rating",algorithm="MD5",cnonce="a1f74260843b54d3b773c4bf84b7ae5c",nc=00000001,qop="auth",response="8086d2cbc3bb9b20425f9a66f5443e98",opaque="W01Tt4kCQ+qOe2Oo6O6vGg=="

This is the new one:

Authorization: Digest username="jmartine", realm="musicbrainz.org",  
nonce="ot3KqbreS0mgD/O/Eqij4w==",  
uri="/ws/2/rating?client=StarMyGrooves-1.0", algorithm=MD5,  
response="28da1f0ed9c2647561f7732d92eea1d2", qop=auth,auth-int,  
nc=00000001, cnonce="2615318"

The immediate problem seems to be that opaque is missing (it should  
echo the value sent from the server), but having "auth,auth-int" seems  
also suspicious.

Ulrich