Difference between revisions of "Patch - Fix captive portal non-standard HTTP port redirect"
From Edge Threat Management Wiki - Arista
Jump to navigationJump to search (Created page with "When the HTTP port on the Config/Services/Local Services page is configured for a value other than the standard/default port 80, captive portal will incorrectly include the po...") |
m |
||
| Line 1: | Line 1: | ||
| − | When the HTTP port on the Config/Services/Local Services page is configured for a value other than the standard/default port 80, | + | = What it is = |
| + | |||
| + | When the HTTP port on the Config/Services/Local Services page is configured for a value other than the standard/default port 80, Captive Portal will incorrectly include the port twice when generating the captive page redirect for unauthenticated clients. This prevents the proper display of the Captive Page. | ||
| + | |||
| + | = Target Version = | ||
| + | |||
| + | 13.1.0 | ||
| + | |||
| + | = How to run = | ||
| + | |||
| + | <code> | ||
| + | curl -k http://download.untangle.com/patches/generic/capture_redirect_port_fix.sh | dash | ||
| + | </code> | ||
Revision as of 22:57, 17 October 2017
What it is
When the HTTP port on the Config/Services/Local Services page is configured for a value other than the standard/default port 80, Captive Portal will incorrectly include the port twice when generating the captive page redirect for unauthenticated clients. This prevents the proper display of the Captive Page.
Target Version
13.1.0
How to run
curl -k http://download.untangle.com/patches/generic/capture_redirect_port_fix.sh | dash
