Return-Path: 
 <tomcat-dev-return-55134-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org
Received: (qmail 70873 invoked from network); 19 Jan 2005 09:43:06 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 19 Jan 2005 09:43:06 -0000
Received: (qmail 49947 invoked by uid 500); 19 Jan 2005 09:43:00 -0000
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 49911 invoked by uid 500); 19 Jan 2005 09:42:59 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 49898 invoked by uid 99); 19 Jan 2005 09:42:59 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FORGED_RCVD_HELO,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of julian.reschke@gmx.de
 designates 213.165.64.20 as permitted sender)
Received: from mail.gmx.de (HELO mail.gmx.net) (213.165.64.20)
  by apache.org (qpsmtpd/0.28) with SMTP; Wed, 19 Jan 2005 01:42:58 -0800
Received: (qmail invoked by alias); 19 Jan 2005 09:42:55 -0000
Received: from pD9535794.dip.t-dialin.net (EHLO [192.168.0.2]) (217.83.87.148)
  by mail.gmx.net (mp010) with SMTP; 19 Jan 2005 10:42:55 +0100
X-Authenticated: #1915285
Message-ID: <41EE2B9A.3030806@gmx.de>
Date: Wed, 19 Jan 2005 10:42:50 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Expect: 100-continue
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Hi,

Looking at <http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4812000>:

--
DESCRIPTION OF THE PROBLEM :
The servlet API provides no means of controlling the 100- continue 
response when the user agent expects it, and doesn't specify when it is 
or is not sent by the servlet container. It should do so.  One 
suggestion to handle this would be:

1. Add a method to HttpServletRequest called acceptRequest or some such, 
which causes a 100-continue to be sent. acceptRequest would have no 
effect if the user agent doesn't expect a 100-continue.

2. Specify that 100-continue will not be sent until one of the following 
happens to the request object:

    a. acceptRequest() is called
    b. getInputStream() or getReader() is called
    c. For the POST method, getParameter() or similar is called.

This would be compatible with the current specification (though not with 
current tomcat, which always sends 100- continue immediately), but 
provide the ability for better control.
--

Does Tomcat5 (or 4, for that matter) actually implement one of these 
options (2b&c, for instance)?

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org