6 ms·
Not sure. Perhaps the session-ID is when the user hits an HTTP landing page (and captured then) and the server reuses it when forwarditng/linking them to HTTPS
by Terr_ 12y ago
Not sure. Perhaps the session-ID is when the user hits an HTTP landing page (and captured then) and the server reuses it when forwarditng/linking them to HTTPS content?
You could set the "secure" flag on the cookies so that the browser only repeats them to HTTPS endpoints, but that won't help if the original header to set the cookie is sent out over HTTP.