Welcome! Log In Create A New Profile

Advanced

FIN/ACK closes upstream connection for HTTP, but not for HTTPS

Jeremy Apthorp
February 24, 2011 09:18AM
I'm running nginx as a reverse proxy to do SSL and load balancing. The
upstream server behind nginx needs to know when the client closes the
connection.

If I turn ssl off, the connection looks like:

1. client connects to nginx
2. nginx connects to upstream
3. ...
4. client sends FIN/ACK to nginx
5. nginx sends FIN/ACK to upstream, and to client


With ssl on:

1. client connects to nginx
2. nginx connects to upstream
3. ...
4. client sends FIN/ACK to nginx
5. nginx waits 60 seconds
6. nginx sends FIN/ACK to upstream



What's going on here? Why does nginx wait for a timeout to send the FIN/ACK
upstream? Why does the behaviour change when I turn ssl on?


Thanks,
Jeremy
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

FIN/ACK closes upstream connection for HTTP, but not for HTTPS

Jeremy Apthorp February 24, 2011 09:18AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 343
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready