What do you see in the Set-Cookie header on the client when the 302 response is sent?
Maybe use 1/1/1970 instead of -1? Here's an example that worked for me previously. I set the cookie value to the string "null", to test. I suppose it shouldn't matter though.
HTTP::respond 302 Location http://$::host$::default_redirect_path Set-Cookie "${::session_cookie_name}=null\;Expires=Thurs, 01-Jan-1970 00:00:00 GMT"
Also, the TCL error you have listed above is because you were referencing IP::server_addr when a server side connection hadn't been established. If the log statement using IP::server_addr was in an event where the server side connection should normally be there, you can try to log it without causing the TCL error using catch (
Click here).
if {[catch {IP::server_addr}] server_ip}{
There was an error running IP::server_addr, so don't try to log the value
log local0. "No serverside connection"
} else {
No error. There was a serverside connection, so the value is saved in $server_IP
log local0. "\$server_ip: $server_ip"
}
Lastly, the bigd SSL routines error being logged is probably from a misconfigured HTTPS monitor, or an HTTPS monitor polling a non-HTTPS server.
Aaron