bugGNU Wget - Bugs: bug #20545, Wget should choose the strongest...

 
 

bug #20545: Wget should choose the strongest auth mechanism offered

Submitted by:  Micah Cowan <micahcowan>
Submitted on:  Fri 20 Jul 2007 09:12:53 PM UTC  
 
Category: Protocol IssueSeverity: 4 - Important
Priority: 5 - NormalStatus: Duplicate
Privacy: PublicAssigned to: Micah Cowan <micahcowan>
Originator Name: Open/Closed: Closed
Release: NoneOperating System: None
Reproducibility: NoneFixed Release: None
Planned Release: 1.12Regression: None
Work Required: 0 - HoursPatch Included: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 01 Aug 2007 04:30:47 AM UTC, comment #1:

Using bug 20607 to track general Auth RFC non-compliance issues.

Micah Cowan <micahcowan>In charge of this item.
Fri 20 Jul 2007 09:12:53 PM UTC, original submission:

AIUI, wget currently just chooses the first auth mechanism it recognizes from the challenge list (actually, at the time of this writing, it sends Basic automatically, without challenge).

Wget needs to follow the requirements of RFC 2617 and choose the strongest auth mechanism it understands, not just the first one it encounters that it understands.

Micah Cowan <micahcowan>In charge of this item.

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by micahcowan (Submitted the item)
  •  

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 01 Aug 2007 04:30:47 AM UTCmicahcowanStatusConfirmed=>Duplicate
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1