-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hector wrote:
> In the same way GOOGLE uses a COOKIE to be persistent for a certain > web page and applies redirection logic or not based on whether the > browser passed a authorized cookie: header, GOOGLE should do the > same thing with Chrome with standard HTTP authorization headers. If you are using http-auth as a cookie replacement you could just replace the code which sends 401 with code sending a session cookie instead and replace the code that checks for the authorization header and loads the session data with code that checks for the cookie header instead. ~10 lines of code. This would solve your problem immediately. - -- private communication within hostile networks: http://torchat.googlecode.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI2TygxT6R4jlFoh0RAnwTAKC/weYvi81cOh3YU3RK5UiSZOvTygCfeFh3 kd2dMi2Elm77CR1TgFVk55I= =6+Kl -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
