The same trouble with Windows Internet Explorer 7.0.5730.13 (RU) that we'r
received automatically via WSUS3 :(((
The far end is Apache/2.0.50 (FreeBSD), PHP/4.3.11.
It's strange - there'r no more such discussions in web, but this problem is
ACTUALLY EXIST.
2 day sniffer usage is really crashing my brain... :) lot of new headers,
added line feed after 'Digest' but no any serious differences I see...
We'r need help.

"Ronan" wrote:
> ... I cannot use it with our intranet application (hosted on apache 2.0.53 with digest authentication)
> Rq: it works previsiously with IE6 ...
> IE7 send GET / (without Authorization: obviusly)
> Apache answer HTTP/1.1 401 (with WWW-Authenticate: Digest ...)
> IE7 answer with an Authorization: header
> Apache answer HTTP/1.1 200 and my html page
> ...
> My site is in trusted site !

"kay27" <kay27@discussions.microsoft.com> wrote in message
news:AE6ED774-C90C-4356-9B3B-528FD1163702@microsoft.com...
> The same trouble with Windows Internet Explorer 7.0.5730.13 (RU) that we'r
> received automatically via WSUS3 :(((
> The far end is Apache/2.0.50 (FreeBSD), PHP/4.3.11.
> It's strange - there'r no more such discussions in web, but this problem is
> ACTUALLY EXIST.
> 2 day sniffer usage is really crashing my brain... :) lot of new headers,
> added line feed after 'Digest' but no any serious differences I see...
> We'r need help.


There was a problem in IE6 when the URL involved an anchor string
(e.g. the wrong digest was calculated). Perhaps your server was ignoring
that error but now that is fixed in IE7 it is seeing a correct response as an
error? ; )

BTW this is not the best newsgroup to be discussing web development
issues. Try the appropriate MSDN web forum instead.


Good luck

Robert Aldwinckle
---


>
> "Ronan" wrote:
>> ... I cannot use it with our intranet application (hosted on apache 2.0.53 with digest authentication)
>> Rq: it works previsiously with IE6 ...
>> IE7 send GET / (without Authorization: obviusly)
>> Apache answer HTTP/1.1 401 (with WWW-Authenticate: Digest ...)
>> IE7 answer with an Authorization: header
>> Apache answer HTTP/1.1 200 and my html page
>> ...
>> My site is in trusted site !

Thanx for your response... Server is 'far end' and it is not _mine_ :( so I
have nothing to do...
%systemroot%\ie7\spuninst\spuninst.exe and reboot helps... :)

I think, web server's owner must contact Microsoft to get support and to
find solution for his server... What to me, I look for client-side solution:
patch, tweak, registry key, etc, but it seems like there's nothing more to
do... (?)

"Robert Aldwinckle" wrote:

> There was a problem in IE6 when the URL involved an anchor string
> (e.g. the wrong digest was calculated). Perhaps your server was ignoring
> that error but now that is fixed in IE7 it is seeing a correct response as an
> error? ; )
>
> BTW this is not the best newsgroup to be discussing web development
> issues. Try the appropriate MSDN web forum instead.

Did anyone find a solution for this issue? I reposted under the title
"Automatic logon with current username and password". Here's the facts.
1. Set browser security to use the above.
2. Log in to a secure site.
3. Navigate around the site for a while.
4. After 5-10 minutes, the user is forced to re-authenticate

Where is the timeout value? I've searched the registry for months and
turned up nothing.

Robert posted an URL to changes in https security in IE7, but this is not
addressed, and some recommendations (https:// to :// do not help).

I'm accessing a Digest-authenticated IIS 6 site served by Windows 2003 SP2
Server. I'm almost certian that this is NOT a server issue, but is instead A
POORLY DOCUMENTED / UNDOCUMENTED IE SETTING Internet Explorer issue.

It would help to be able to increase the value between re-authentications to
a longer period. Does anyone on planet Earth know how to effect this timeout
period?

"kay27" wrote:

> Thanx for your response... Server is 'far end' and it is not _mine_ :( so I
> have nothing to do...
> %systemroot%\ie7\spuninst\spuninst.exe and reboot helps... :)
>
> I think, web server's owner must contact Microsoft to get support and to
> find solution for his server... What to me, I look for client-side solution:
> patch, tweak, registry key, etc, but it seems like there's nothing more to
> do... (?)
>
> "Robert Aldwinckle" wrote:
>
> > There was a problem in IE6 when the URL involved an anchor string
> > (e.g. the wrong digest was calculated). Perhaps your server was ignoring
> > that error but now that is fixed in IE7 it is seeing a correct response as an
> > error? ; )
> >
> > BTW this is not the best newsgroup to be discussing web development
> > issues. Try the appropriate MSDN web forum instead.