-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hector wrote:
> You didn't follow the problem: I followed the problem very well: You are relying on an optional feature that browsers may or may not implement. you are sending a 301 on your front page and the Browser does what is expected: It redirects. Instead you should just send a 401 instead and if the browser then answers with the correct "Authorization"-header you send the actual content. Shouldn't more than 5 lines of code in the base class for all your page controllers/request-handlers/whatever. - -- 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 iD8DBQFI2TQixT6R4jlFoh0RAi51AJ9HHMf7/Wlkas9PYOn7uJwwDA+JpQCcCIUA s6N1PqfHYYYgzEctMWDob7Y= =oRNL -----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 -~----------~----~----~----~------~----~------~--~---
