X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id DE7879DC8DC
	for <pgsql-www-postgresql.org@localhost.postgresql.org>;
	Fri, 20 Jan 2006 18:19:16 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 89658-07
	for <pgsql-www-postgresql.org@localhost.postgresql.org>;
	Fri, 20 Jan 2006 18:19:17 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158])
	by postgresql.org (Postfix) with ESMTP id D2CB39DC83F
	for <pgsql-www@postgresql.org>; Fri, 20 Jan 2006 18:19:11 -0400 (AST)
Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1])
	by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id k0KMJAVG021783
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <pgsql-www@postgresql.org>; Fri, 20 Jan 2006 15:19:13 -0700 (MST)
	(envelope-from mfuhr@winnie.fuhr.org)
Received: from winnie.fuhr.org (localhost [127.0.0.1])
	by winnie.fuhr.org (8.13.4/8.13.4) with ESMTP id k0KMJAj3086196
	for <pgsql-www@postgresql.org>; Fri, 20 Jan 2006 15:19:10 -0700 (MST)
	(envelope-from mfuhr@winnie.fuhr.org)
Received: (from mfuhr@localhost)
	by winnie.fuhr.org (8.13.4/8.13.4/Submit) id k0KMJApd086195
	for pgsql-www@postgresql.org; Fri, 20 Jan 2006 15:19:10 -0700 (MST)
	(envelope-from mfuhr)
Date: Fri, 20 Jan 2006 15:19:10 -0700
From: Michael Fuhr <mike@fuhr.org>
To: pgsql-www@postgresql.org
Subject: Searches resulting in 414 Request URI too long
Message-ID: <20060120221910.GA86040@winnie.fuhr.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.106 required=5 tests=[AWL=0.106]
X-Spam-Score: 0.106
X-Spam-Level: 
X-Archive-Number: 200601/221
X-Sequence-Number: 9409

A few times in the past day I've gotten 414 (Request URI too long)
errors while searching through the mailing list archives.  I haven't
figured out a 100% repeatable test case yet, but you can eventually
see what's happening by doing the following:

1. Go to http://archives.postgresql.org/

2. Search for something (e.g., "foo").

3. Move between result pages by clicking Next, Previous, or one of
   the page numbers.  Do this several times and eventually the URI
   gets excessively long.  Sometimes it happens right away but
   sometimes it requires numerous clicks.

The A tags for the result pages' links go from something like

<a href="?q=foo&cs=utf-8&fm=on&gr=off&st=20&np=1">

to

<a href="?q=foo&ul=http%3A%2F%2Farchives.postgresql.org%2Fpgsql-bugs%2F%25&cs=utf-8&fm=on&gr=off&st=20&np=2">

and then they get longer, with numerous instances of "ul=...".
Eventually they get too long and the web server responds with
414 Request URI too long.

-- 
Michael Fuhr