Getting back to the original subject:
Assuming you're doing standard HTTP Authentication, it doesn't work
that way. Once you get the login popup, every subsequent request by
the browser sends the same authentication token (username password
in clear text) to the server.
You're right - the
On Tue, Jul 14, 2009 at 6:23 AM, Paul Reillyparei...@tcd.ie wrote:
Getting back to the original subject:
Assuming you're doing standard HTTP Authentication, it doesn't work
that way. Once you get the login popup, every subsequent request by
the browser sends the same authentication token
Hello,
Is there a recommended solution for redirecting clients which need
to authenticate for .htacess to a secure version of the URL, and then
following succesful authentiction, redirecting them back to the normal
(port 80) URL ?
I've seen code like the following
Directory
On Tue, Jul 7, 2009 at 10:25 AM, Paul Reillyparei...@tcd.ie wrote:
I don't want to force all web access over HTTPS, just the .htaccess
authentication.
Assuming you're doing standard HTTP Authentication, it doesn't work
that way. Once you get the login popup, every subsequent request by
the
