[Http-use] HTTP_CONNECT Request msg
riyaz talikoti <riyazinbec@gmail.com> Wed, 02 February 2022 15:25 UTC
Return-Path: <riyazinbec@gmail.com>
X-Original-To: http-use@ietfa.amsl.com
Delivered-To: http-use@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB5A3A120D for <http-use@ietfa.amsl.com>; Wed, 2 Feb 2022 07:25:21 -0800 (PST)
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 eCqSkYGNNtYy for <http-use@ietfa.amsl.com>; Wed, 2 Feb 2022 07:25:20 -0800 (PST)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 D0ABD3A1207 for <Http-use@ietf.org>; Wed, 2 Feb 2022 07:25:16 -0800 (PST)
Received: by mail-yb1-xb32.google.com with SMTP id j2so48882937ybu.0 for <Http-use@ietf.org>; Wed, 02 Feb 2022 07:25:16 -0800 (PST)
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=zFkTd3R49UtttWRHTuC0T0KSmC0diwmknfQ8WYFxTM0=; b=RRWxnXWcVXoDwjPpftreLXkePwXWiT+zY22RLXC1SPR1iimy2u5mLsKWzM8zdEuaTx VDreuhCQBsupuNs4NxMwQybyMK3XZ+Ib2LwNv+T4JTreUbYHlb3L41Oy6FewZrWMUF6F MvqkkgQQ+oMfBygssSh5/No8YcUlwZesk8TosiIlROAFy3AzLL4bitTO3pZtohozoNmo nAWUqzQMFzajwSZ2rrfQDKC7DcqECqUk9pIDM8rLFLptbDQQ1JZCbUzs7V3uiyc+xAUp m7EHbp8WQ4BXdX7uvx3RnW//PEOxclvD47fQ0EIyXScRZeOBZnwLmzTwFSPcreErLC3q qhSA==
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=zFkTd3R49UtttWRHTuC0T0KSmC0diwmknfQ8WYFxTM0=; b=H5ZFKCSNdgEn5mt70oh4xxMx4O3K+lqvmqZThBF3ue4p4MrqFiGWOMgowSseTApa1X 1ajN67Q/d+EItIbyXffhw4FMJAXKpw4JCXRQBXd3PhB0I2Cq+9RbATKZjplXQ/v6KLch ENU+lPNuYO2rWCIUTEnrXVLSrrwrLZ8zrzuTtvDZ+XlSKlXz4MgkqiGRGNAT0yNW3l/v VbZKcILcRV/AZWZ0ySjSMZEaYtLSSJcFMB8/KQ7QxW6H94Y40wt8IiN04M4vdcGy7bDc n9dzeBHv/7LuFXFofEfHnyU1FqVTLMiMy6+aN1IzDNr3JJprv+8uVTSRVJ+L8qHrQiB8 CkXw==
X-Gm-Message-State: AOAM533C8+fqBpXFQGg/qZ5+qrx7vN9ks1tbuv18QxcLhE6zDCTxgxbY 5saAVkTenQU80dGIwySbt4Sr4q6zdzQ+KdCzQMI7nZi3aUY=
X-Google-Smtp-Source: ABdhPJwRvNcP1U7bSKPqJVMoGNc+RycLTsu7R/sZKtLFbD/6QNaJQhMuDGs49KoF/e1UmZomOGFqxiLlwEdb4Ns4iX0=
X-Received: by 2002:a0d:c2c4:: with SMTP id e187mr1342851ywd.294.1643815514930; Wed, 02 Feb 2022 07:25:14 -0800 (PST)
MIME-Version: 1.0
From: riyaz talikoti <riyazinbec@gmail.com>
Date: Wed, 02 Feb 2022 20:55:04 +0530
Message-ID: <CADJ+CdYfcDopMCao=ED9gtLo9BWny7UmZtZ1bLo0gqGBanG+oA@mail.gmail.com>
To: Http-use@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d8002405d70a9fe9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-use/CM1rKk7ZENHe_S5aJYOJDTiNhho>
Subject: [Http-use] HTTP_CONNECT Request msg
X-BeenThere: http-use@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion and review of IETF protocols that use HTTP and related Web technologies \(sometimes called \"RESTful\" protocols\)" <http-use.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-use>, <mailto:http-use-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-use/>
List-Post: <mailto:http-use@ietf.org>
List-Help: <mailto:http-use-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-use>, <mailto:http-use-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2022 15:25:21 -0000
Dear Team, I had a basic doubt with http connect request when proxy is enabled. Post TCP connection 1. HTTP CONNECT will be the FIRST packet always when proxy is enabled on the client to a particular web-server? 2. There is no use case where connect can be sent in-between (after other REQUEST msgs)? Appreciate the Response Regards Riyaz
- [Http-use] HTTP_CONNECT Request msg riyaz talikoti