[Wish] should we remove the support for http redirections on initial PUT request?

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 13 September 2021 14:44 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: wish@ietfa.amsl.com
Delivered-To: wish@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B4A3A0967 for <wish@ietfa.amsl.com>; Mon, 13 Sep 2021 07:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9KrVaCcdJET for <wish@ietfa.amsl.com>; Mon, 13 Sep 2021 07:44:39 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 355873A0964 for <wish@ietf.org>; Mon, 13 Sep 2021 07:44:39 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id m26so9064399pff.3 for <wish@ietf.org>; Mon, 13 Sep 2021 07:44:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=6F5vzx0fF1/LwLgQUuvLE2e9rUXlvdh20RFDFf22GKU=; b=gDWMGgWXurYoasRP0VGYZ7AlWyg2whLswSnLHQORmyea08N6kvfXFMjZWXvw6PGHTj ZjbagDpSHLBhljiN8ppyM1BR/1FGVceOGjlL4WnW21N01tJzFGInEZAAHmyVlYhngrmM xGUe9R8mTaSC5WJjSLgvwmU1vT7kmVEiApBIIILJVewGowZkLJxYcOnVxn3EtliH9wGH NhqeiQQvS55B90bDU/TDC2IU1vKWGIR7VGpOxGOZjcpjuxgQ/sO6NpmiirEJt7VpDWmq 940KVHheYXvLX/TptLZJ41uvlOcV45jsXdLZ3yxw4yZaceARz9kaFdmpIDqcqqFJKccF ayRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6F5vzx0fF1/LwLgQUuvLE2e9rUXlvdh20RFDFf22GKU=; b=ae2X6OcUPXO9HSi4+v9J10UW3tK3XV22nSo1TWzC9f7Fyh0KyYLd2/qzevGdRXGM+R ZqVENkuyQof9LpD4yBMhJihiotnr8nVsN0DQsvg8RJSUQx6QeNYbBeiGH5cn4fsJ4rmM CsnrS9Pmjjj4lzFDYvfaMkIQEjTqVJ9rVXsaCFnDRogEoux88RJcIXHD0M4R/u5+ox+5 uAfyZIdKHjKWrdR3oq9H3DYwp2To3G3bwVifiZiDTxaO9fc60H2nOiFP8ZhQbITK92qX zGIYqr/cg+rqlllyuvIavdmWGVYZS6rPQUHEpE+Od4+liGiCuO+M329nUl68y+aCea4x DxNA==
X-Gm-Message-State: AOAM530xbQtaPMK0F51OPwViyRHbnToZrtZpuSEpybySJ+EKb/bQDpZU G/G7XSZpvkFWt0nNmxmvHJDDG+QMA0e2mcG5ARkNzeTlW5o=
X-Google-Smtp-Source: ABdhPJzAEOoOPqnZPMDhFiAP4Il/tIGF0ouCV+UgD1UhLd971F5yEIb9pgkVMD9LnUjz8vcTG+sQ2VbqaDpufdokfQU=
X-Received: by 2002:a63:6d46:: with SMTP id i67mr11350505pgc.308.1631544277539; Mon, 13 Sep 2021 07:44:37 -0700 (PDT)
MIME-Version: 1.0
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Mon, 13 Sep 2021 16:44:26 +0200
Message-ID: <CA+ag07ZM3_UYYSZpRuyJ0ONy9g_C3sYYXVSqVEk-SdUK9tcPOQ@mail.gmail.com>
To: WISH List <wish@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000019202105cbe18131"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/P2CEA-Yp--6Q85cC7yzlTmodZ3o>
Subject: [Wish] should we remove the support for http redirections on initial PUT request?
X-BeenThere: wish@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: WebRTC Ingest Signaling over HTTPS <wish.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wish>, <mailto:wish-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wish/>
List-Post: <mailto:wish@ietf.org>
List-Help: <mailto:wish-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wish>, <mailto:wish-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2021 14:44:43 -0000

Hi all,

On the draft, it is stated that:

WHIP endpoints and media servers MAY not be colocated on the same server so
it is possible to load balance incoming requests to different media
servers. WHIP clients SHALL support HTTP redirection via 307 Temporary
Redirect response code.

However, http clients are not handling the redirection automatically as it
is a PUT request with body and not a GET request. I am not sure if
supporting this makes much sense anymore, does anyone plan to use it or we
should remove it from the draft?

Best regards
Sergio