IETF Logo Mail Archive

Re: [Captive-portals] Capport return of experience and... questions :(

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 18 July 2022 16:38 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: captive-portals@ietfa.amsl.com
Delivered-To: captive-portals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C57DDC134859 for <captive-portals@ietfa.amsl.com>; Mon, 18 Jul 2022 09:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oHcKf9HvwXeh for <captive-portals@ietfa.amsl.com>; Mon, 18 Jul 2022 09:38:05 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27D97C138FCA for <captive-portals@ietf.org>; Mon, 18 Jul 2022 09:38:01 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [207.164.179.98]) by relay.sandelman.ca (Postfix) with ESMTPS id D09221F459; Mon, 18 Jul 2022 16:37:58 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id CAE781A0461; Mon, 18 Jul 2022 12:37:55 -0400 (EDT)
Received: from dooku (localhost [127.0.0.1]) by dooku.sandelman.ca (Postfix) with ESMTP id C96AF1A01C4; Mon, 18 Jul 2022 12:37:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Xavier BEAUDOUIN <xbeaudouin=40hotcity.lu@dmarc.ietf.org>
cc: captive-portals@ietf.org
In-reply-to: <B3500D35-B44E-47C9-BEAB-3D69EF4B8C0B@hotcity.lu>
References: <B3500D35-B44E-47C9-BEAB-3D69EF4B8C0B@hotcity.lu>
Comments: In-reply-to Xavier BEAUDOUIN <xbeaudouin=40hotcity.lu@dmarc.ietf.org> message dated "Mon, 18 Jul 2022 16:47:28 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 18 Jul 2022 12:37:55 -0400
Message-ID: <1281989.1658162275@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/Xat2jf9CASeXL5DiXh9ANyKj2i0>
Subject: Re: [Captive-portals] Capport return of experience and... questions :(
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of issues related to captive portals <captive-portals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/captive-portals/>
List-Post: <mailto:captive-portals@ietf.org>
List-Help: <mailto:captive-portals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2022 16:38:06 -0000

Xavier BEAUDOUIN <xbeaudouin=40hotcity.lu@dmarc.ietf.org> wrote:
    > We are a national Wi-Fi provider in Luxembourg and we provide public
    > Wi-Fi hostpots all around the country (~20K users / day).  Few weeks

Wow, thank you so much for doing this... I'm sorry that it caused problems...

    > # The device requested 2 times the captive portal
    > landing page too # Notes :

That seems weird.

    > # * The user has just activated his wi-fi
    > session (his state passes from captive=true to captive=false)
    > # * The
    > device decided to open again the captive portal pop-up without checking
    > for the captivity current state

The thing that I'm thinking about is ETag, Caching, etc. headers on the
replies.  I think that there should never be caching, but it feels like maybe
iOS is caching something.
I can't say if it's a bug or what.

I'm hoping we'll find soneone replying here about this, perhaps offering to
debug this with you.  (This might be a job for the IETF Hackathon
VPN... which does L2 stuff)

    > Unfortunatly we decided to stop support of capport on our national
    > network until we are able to fix a workaround about this.

:-(

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email