Bug 1456005 Comment 8 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by

Valentin Gosu [:valentin] {{ IETF until 25 July - PTO until 3 August }}

on 2019-04-01 07:30:08 PDT

This is useful to prevent issues in TRR mode 2 when a captive portal redirect occurs via DNS.
For example, if we are in an unlocked CP and in suddenly locks, we must make sure that we don't use a cached DNS entry from when the portal was unlocked.
This is especially relevant in split horizon situations.

Revision 1 by

Valentin Gosu [:valentin] {{ IETF until 25 July - PTO until 3 August }}

on 2019-04-01 07:34:34 PDT

This is useful to prevent issues in TRR mode 2 when a captive portal redirect occurs via DNS.
For example, if we are in an unlocked CP and in suddenly locks, we must make sure that we don't use a cached DNS entry from when the portal was unlocked.
This is especially relevant in split horizon situations.

This isn't useful in TRR mode 3, as the flag would just cause the resolution to fail.
For that we need to add the captive portal URI to the TRR exclusion list.

Back to Bug 1456005 Comment 8