Forum Discussion
heskez_36146
Jan 06, 2015Nimbostratus
Now I notice a SYN on the firewall's outside interface with port 80 and a ACK on the firewall's inside interface on port 443. (I was expecting port 80)
22.055425 ipwebapp.50168 -> publicip.443: 3767854316 ack 2377740293 22.086639 ipwebapp.50169 -> publicip.443: 1586917823 ack 4126254047
So It look likes the 443 request lands on the Loadbalancer. The certificate is offloaded and send a session on port 80 HTTP to the webserver, but the webserver replies at port 443 and that's probably the reason the session is broken and the error message shows.
No the question is why does the webserver try to setup a session back at port 443?