277822 - Incomplete digest authentication processing.

Status: RESOLVED DUPLICATE of bug 116177

(Firefox :: General, defect)

Description

[Hans Verschoor]

The problem is that the Authentitcation-Info trailer is not processed when added
to an HTTP response message. I observed this behaviour in the Windows and Linux
versions of FireFox. In the Linux versions of Firefox I observed wrong
incrementation (2 instead of 1) of the nonce count. I did not test this under
Windows yet.
The document in the URL ( http://www.xs4all.nl/~hanjen/md5/Leach.html ) reports
the same problem in Microsofts Internet Explorer. Other failures mentioned in
this document have not been tested.
For Mozilla, sending an 401 response with "stale=true" may still invoke a login
popup in FireFox, I'm not sure about this.

Comment 1

[Jo Hermans]

(In reply to comment #0)
> The problem is that the Authentitcation-Info trailer is not processed when added
> to an HTTP response message. I observed this behaviour in the Windows and Linux

Can you specify what exactly isn't processed ? There are several open bugs, like
bug 116177 (nonces), bug 168942 (qop=auth-int) or bug 270447 (Md5-sess & cnonce).

> versions of FireFox. In the Linux versions of Firefox I observed wrong
> incrementation (2 instead of 1) of the nonce count. I did not test this under
> Windows yet.

bug 114451

> The document in the URL ( http://www.xs4all.nl/~hanjen/md5/Leach.html ) reports
> the same problem in Microsofts Internet Explorer. Other failures mentioned in
> this document have not been tested.
> For Mozilla, sending an 401 response with "stale=true" may still invoke a login
> popup in FireFox, I'm not sure about this.

Comment 2

[Hans Verschoor]

I downloaded the FireFox source and performed a scan for Authentication-Info. 
The scan only revealed one instance in a comment.
So now I am convinced the Authentication-Info header is not processed indeed, 
not in FireFox (or Microsoft Internet Explorer). That leaves another essential 
question: are headers at the end of the HTTP response (following a chunked 
body, see RFC2616) processed at all ?

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Jo Hermans]

*** This bug has been marked as a duplicate of 116177 ***