Project

General

Profile

Actions

Bug #6421

closed

Nginx keepalive_timeout 65 breaking some captive portal redirects

Added by Chris Linstruth over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
Captive Portal
Target version:
Start date:
05/31/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

Using nginx as the captive portal web server with keepalive_timeout 65 causes attempts to access sites after authentication to use same TCP/HTTP session to captive portal instead of a new session to the destination site. This gives the appearance of not being redirected to the destination site after login with the portal page just "hanging" after login is pressed. This only manifests itself if the same destination site is attempted by the client both pre- and post-auth.

Setting keepalive_timeout 0 in the portal nginx config forces clients start a new TCP/HTTP session for each web element and corrects this. A short but > 0 value like 1 or 2 should keep most of the keepalive benefits during portal page load yet cause new TCP sessions to be used after all but very quick portal logins.

It looks like lighttpd had:

server.max-keep-alive-requests = 15
server.max-keep-alive-idle = 30

I am not certain but this could explain some of the strange login hangs/timeouts I used to see.

Actions

Also available in: Atom PDF