Re: [hybi] Proposal for a clean way to detect non-HTTP compliant transparent proxies

Greg Wilkins <gregw@webtide.com> Thu, 22 July 2010 01:00 UTC

Return-Path: <gregw@webtide.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AC143A6951 for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 18:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.808
X-Spam-Level:
X-Spam-Status: No, score=-1.808 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dj6y2WdFDuUL for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 18:00:46 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 4BBDB3A6838 for <hybi@ietf.org>; Wed, 21 Jul 2010 18:00:46 -0700 (PDT)
Received: by fxm1 with SMTP id 1so4377557fxm.31 for <hybi@ietf.org>; Wed, 21 Jul 2010 18:01:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.103.72 with SMTP id j8mr1182594fao.4.1279760462503; Wed, 21 Jul 2010 18:01:02 -0700 (PDT)
Received: by 10.223.112.129 with HTTP; Wed, 21 Jul 2010 18:01:02 -0700 (PDT)
In-Reply-To: <20100722003801.GJ14589@shareable.org>
References: <20100721225210.GE6475@1wt.eu> <20100722003801.GJ14589@shareable.org>
Date: Thu, 22 Jul 2010 11:01:02 +1000
Message-ID: <AANLkTilQVmOCtejAJ7xccv5bCX5rTbakB6qFY5X9yxMN@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Jamie Lokier <jamie@shareable.org>
Content-Type: multipart/alternative; boundary="001636c5bb74c3e1ca048bef737f"
Cc: hybi@ietf.org
Subject: Re: [hybi] Proposal for a clean way to detect non-HTTP compliant transparent proxies
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2010 01:00:47 -0000

On 22 July 2010 10:38, Jamie Lokier <jamie@shareable.org> wrote:

> There's some discussion on another list about using a 1xx response to
> indicate "request is being processed", for when the processing is slow
> to produce a response.  The fact that is being taken seriously
> suggests that at least some deployments do forward 1xx messages in the
> way the standard requires.
>


We have users that definitely use the 102 processing response with success.
So there must be some network segments where this is possible.
I've often thought that if 102 responses could have bodies and were exposed
to the browser, then they would make an useful transport for comet style
applications.

cheers