Maybe a new component options would let the developer select the behaviour ?
Or maybe first try with on option and then automatically switch to the other
if it fails ?
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Compon
Arno Garrels wrote:
> Paul Read wrote:
>> THanks for that information I therefore tweaked
>> 'AuthDigestParseChallenge' so that Info.Qop is set to 'auth' if no
>> Qop value is given and now the right MD5 is calculated and the server
>> accepts the data.
>
> I'd say this is a server-side bug.
Tho
Hello,
This is what MSDN says about it :
The qop-options directive, as specified in [RFC2617] section 3.2.1, is
optional; but it is used for backward compatibility with digest access
authentication, as specified in [RFC2069]. The qop-options directive
SHOULD be used by all implementations com
Paul Read wrote:
> THanks for that information I therefore tweaked
> 'AuthDigestParseChallenge' so that Info.Qop is set to 'auth' if no Qop
> value is given and now the right MD5 is calculated and the server
> accepts the data.
I'd say this is a server-side bug. It obviously understands a RFC 2617
THanks for that information I therefore tweaked
'AuthDigestParseChallenge' so that Info.Qop is set to 'auth' if no Qop
value is given and now the right MD5 is calculated and the server
accepts the data.
Whether this is a correct thing to do or not is a different matter!
Thanks again for your
