> > Trying to pass the buck to our WINSERVER (Wildcat! Interactive Net
> > Server) Web Server component is unacceptable.
>
> If I were you I would just patch my server so that it works with all
> browsers instead of trying to effect a change of the protocl definition
> and its implementation in all existing browsers.

For the record, Safari and Chrome, which is really just one because
they both use the same source code, are the only browsers broken in
the matter.

You didn't follow the problem:

Any operator or web site issuing a redirection, whether its our web
server, IIS, apache, etc, Chrome will fail to send the authorization
header as it suppose to.  All others do, including the TrollTech' s QT
implementation of WebKit.

Simply put Chrome will have problems in web site settings using
secured HTTP BASIC/DIGEST authentication.

Hector Santos/CTO
Santronics Software, Inc
http://www.santronics.com



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to