I maintain a website that uses basic authentication to prevent outside users from viewing it (It's a staging/test environment open to the internet). The website is available over unsecured (HTTP) connections with some pages (like the log in/registration forms) requiring secure (HTTPS) connections. The site has a separate cookie based log in, but this is custom and does not use any framework provided APIs (I.E. Forms Authentication)
In this environment, when a user has successfully logged in to the site homepage via an unsecured connection, then clicks a link to open a secure page, they are prompted to log in again via basic authentication. My client has requested that this second log in be removed.
Is there a way to make the basic authentication persist across the protocol switch (HTTP -> HTTPS) without requiring a log in again?