bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug#4883: 23.1; url-http: wrong server name used for pwd lookup duri


From: Ted Zlatanov
Subject: Re: bug#4883: 23.1; url-http: wrong server name used for pwd lookup during proxy authentication
Date: Tue, 01 Dec 2009 09:20:31 -0600
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux)

On Fri, 27 Nov 2009 22:37:45 +0100 Kai Tetzlaff <address@hidden> wrote: 

KT> On 25.11.2009 15:51, Ted Zlatanov wrote:
>> On Tue, 24 Nov 2009 07:36:43 +0100 Kai Tetzlaff <address@hidden> wrote: 
>> 
KT> I'm not sure why, but also my last post below never made it to the list.
KT> I also sent it to you directly but did not get any reply so i assume
KT> that it also got lost. I don't get why, but i'm trying again.
>> 
>> No worries, this wasn't urgent :)
>> 
KT> In addition to what i wrote below, i've now actually tested the url code
KT> with a double auth. scenario (proxy auth + auth at url target). It
KT> actually works fine without any further changes!
>> 
>> Wonderful.
>> 
KT> When you wrote your message suggesting to rework the patch, what problem
KT> did you had in mind? Is there some other scenario which needs testing?
>> 
>> I thought the double auth might be a problem because the code only takes
>> into account the current auth.  But it works, as you say, and I don't
>> see any side effects.  So I'm in favor of comitting your patch.  I don't
>> know if it's "trivial," however (meaning that it doesn't require
>> copyright assignment papers).  Do you want to propose it on emacs-devel
>> or should I do it?  Either way, you'll get an answer about the copyright
>> papers :)

KT> Thanks for your support and the offer to help with emacs-devel. Actually
KT> Chong Yidong already added the patch to emacs CVS (there's a short note
KT> about it at the very end of the 'Emacs bug Tracking System' post above).
KT> So it seems to have been trivial enough :-).

Wonderful, I didn't see that commit.  I'm glad your change went in.

Ted


reply via email to

[Prev in Thread] Current Thread [Next in Thread]