SSLMiddleware
currently has some SourceForge-specific bits that we should factor out, so anyone can use it.
We should also support secure session cookies, and do so in a way that works with mixed http/https usage. E.g. with a non-secure cookie that acts as a flag indicating a secure session is available and the app can redirect from http->https.
allura:db/7732
SourceForge refactoring lands in forge-classic:db/7732 and config value
force_ssl.logged_in = true
It does not work for me with sfx auth provider. I'm getting redirects to a login page trying to access something unavailable to unauthenticated user (e.g.
/p/test/admin
) and login page says I am already logged in to SourceForge.It works with ldap provider, though.
I guess, since we going to switch sf auth to allura auth soon, that's ok? If it is you can merge this, looks fine to me.
Good catch, I will hold on merging this for a few days.