Closed
Bug 209121
Opened 22 years ago
Closed 22 years ago
Digest authentication incorrectly includes fragment identifier in URI when computing A2
Categories
(Core :: Networking: HTTP, defect, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
mozilla1.5alpha
People
(Reporter: artdodge, Assigned: darin.moz)
Details
(Whiteboard: [digest-auth])
Attachments
(1 file)
|
1.31 KB,
patch
|
dougt
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030521 Galeon/1.3.4 Debian/1.3.4.20030526-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030521 Galeon/1.3.4 Debian/1.3.4.20030526-1
When a URI includes a fragment identifier, e.g.:
http://www.zealforyourhouse.com/authdemo2.php#fragment
Mozilla errantly includes the fragment identifier ("#fragment") in the
digest-uri-value field (uri="...") and when computing A2.
Reproducible: Always
Steps to Reproduce:
1.Go to http://www.zealforyourhouse.com/authdemo2.php
2.Authenticate with username "demo" and password "demo"
3.Use the three links at the bottom; the first behaves normally, the second and
third exhibit the problem behavior.
Actual Results:
The server-side authentication code has to fall back to using the full URI
provided by Mozilla (including fragment identifier) in order to authenticate the
user. The contents of the page present the actual computed digest values.
Expected Results:
Mozilla should have computed A2 (and thus the digest) without including the
fragment identifier ("#frag1") in the Request-URI.
| Assignee | ||
Comment 1•22 years ago
|
||
oops!
Severity: normal → major
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P2
Whiteboard: [digest-auth]
Target Milestone: --- → mozilla1.5alpha
| Assignee | ||
Comment 2•22 years ago
|
||
simple patch
| Assignee | ||
Updated•22 years ago
|
Attachment #127270 -
Flags: superreview?(bzbarsky)
Attachment #127270 -
Flags: review?(dougt)
Comment 3•22 years ago
|
||
Comment on attachment 127270 [details] [diff] [review]
v1 patch
sr=me, but wouldn't
+ if (ref != kNotFound)
+ path.Truncate(ref);
be simpler?
Attachment #127270 -
Flags: superreview?(bzbarsky) → superreview+
| Assignee | ||
Comment 4•22 years ago
|
||
thanks bz.. will do.
Updated•22 years ago
|
Attachment #127270 -
Flags: review?(dougt) → review+
| Assignee | ||
Comment 5•22 years ago
|
||
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•