IETF Logo Mail Archive

Re: Inconsistent behavior of IETF meeting registration page

Bob Hinden <bob.hinden@gmail.com> Thu, 24 May 2012 18:32 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0ED611E80A4 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 11:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NS3oGZBqLDW0 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 11:32:24 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 37A3511E8076 for <ietf@ietf.org>; Thu, 24 May 2012 11:32:24 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so85839qcs.31 for <ietf@ietf.org>; Thu, 24 May 2012 11:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=JQpPfSqi8MIBB4gJs7oq2nB0PYochguJ0yQuO91Q1NY=; b=AS5j4Bn9UwZqBJ+Dn4fkgvaRuV1X9F+xNhqKlCH6PClUs+QRA8UqMzNTFa29I7L1fO 4Su1GmAS73ChLQ4pOzL5ZDe+x10xAan0X9dyCZ5x7zzBHCQQZmjUkjxO2wxqo5KgwD+N oA9GwuX90I9jAqSJ14k/eVzpPj2wmFIDEeQu3lAri11IDbxgG81IMXZRu/wZ8Jg16T3x stReEi5EB/eDuMJIKMcYGG1c4bw6rVujco4lSoY/X6+ynUo+6yZsjWLAUtrQ1rqDvRqt l4vvTnDgEAp3T4cJP0reg0sTB5BAIK8FG6NMhMeGpFR6sPKEOoC43Yc646SgNM6a8cMO tICg==
Received: by 10.50.193.132 with SMTP id ho4mr17464766igc.17.1337884343517; Thu, 24 May 2012 11:32:23 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id k6sm8286891igz.9.2012.05.24.11.32.21 (version=SSLv3 cipher=OTHER); Thu, 24 May 2012 11:32:22 -0700 (PDT)
Subject: Re: Inconsistent behavior of IETF meeting registration page
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAKe6YvMpvZnLTvuJd79woRz=-72WKG6=WmmAk=bExqZjReR46w@mail.gmail.com>
Date: Thu, 24 May 2012 11:32:20 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <A2F13C62-547F-442B-B3B2-7768EA188DC7@gmail.com>
References: <CAKe6YvMpvZnLTvuJd79woRz=-72WKG6=WmmAk=bExqZjReR46w@mail.gmail.com>
To: Vinayak Hegde <vinayakh@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 18:32:25 -0000

Please sent it to <ietf-action@ietf.org>.

Bob

On May 24, 2012, at 10:58 AM, Vinayak Hegde wrote:

> Hi,
> 
> I was trying to register for IETF 84 and tried the link
> http://www.ietf.org/meeting/register.html from the main site.
> Sometimes it takes me to the IETF 80 page (registration over) and
> sometimes it takes me to the right note well page.
> 
> Trying to replicate the issue, I am seeing that it works well on IE
> and Safari on Windows but not on Firefox on Linux/Windows. Further
> attempts to replicate this problem on Firefox on Windows did not work.
> 
> Posting this here as I am not sure what is the right place to post
> such issues. Please point me there. Also hoping that I would get more
> datapoints of this problem from other people on this list (which
> probably will help pinpoint the problem). Looks like a cache-expiry or
> an improper redirection issue.
> 
> Either ways the workaround is to change the number of the IETF meeting
> in the link as this
> (https://www.ietf.org/registration/ietf84/ietfreg.py) works.
> 
> -- Vinayak

v2.23.0 | Report a Bug | By Email