Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 83306 invoked from network); 6 Aug 2010 16:40:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Aug 2010 16:40:59 -0000 Received: (qmail 77664 invoked by uid 500); 6 Aug 2010 16:40:56 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 77585 invoked by uid 500); 6 Aug 2010 16:40:55 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 77577 invoked by uid 99); 6 Aug 2010 16:40:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Aug 2010 16:40:55 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of polaris.ursa@gmail.com designates 209.85.210.45 as permitted sender) Received: from [209.85.210.45] (HELO mail-pz0-f45.google.com) (209.85.210.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Aug 2010 16:40:49 +0000 Received: by pzk10 with SMTP id 10so3194978pzk.18 for ; Fri, 06 Aug 2010 09:40:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=cbFhcxLUd35kKW4KNH0KRsM8ZLNg6+NJRzurc7y+xGw=; b=DdtmXeXVHlG6ZJOQO650gOjJUs7rQ4imyz80eYxA7H2Bq1qDWqHp6EB0aYN9uTWwZ6 ZQqyafYd6LGNvFHsu77T4dRDA5TFvx3F70Ki6rX1hz+OwkJPdeBwpcepjtpE/V54toTs ZrTe7cg1UHrh9MDu25j6nIZAtFoLZOhM09zBA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=JJcI1dPZi79UkfZNlPAz1EJThy1V55RBTu+HcsuRCuL1fSA0NfPwR1jQlAV0EMm4s7 t4nClfU1Easrqoe5FX6YK4EMmxc7C6ew9CfqgRyGnNTYqYRgq8EWG8gYE2Ar0kg9k6Ni Cy7fhkMymLwPQpR6KRAo41EuzmlmArzFSlMws= MIME-Version: 1.0 Received: by 10.114.25.5 with SMTP id 5mr14314925way.78.1281112828829; Fri, 06 Aug 2010 09:40:28 -0700 (PDT) Received: by 10.114.147.19 with HTTP; Fri, 6 Aug 2010 09:40:28 -0700 (PDT) In-Reply-To: References: Date: Fri, 6 Aug 2010 09:40:28 -0700 Message-ID: From: Ursa Polaris To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [users@httpd] Apache/Perl CGI intermittent missing POST data On Fri, Aug 6, 2010 at 3:55 AM, Jeff Trawick wrote: > On Fri, Aug 6, 2010 at 2:50 AM, Timothy Partee = wrote: >> =A0 Basically what's happening is I have a small horde of Perl (not >> mod_perl, just plain Perl) scripts which use the CGI.pm module to >> parse out incoming CGI parameters and cookies, and about 2% of the >> time when I get the POST data params from CGI they are a completely >> empty collection. I can consistently reproduce this with a simple POST >> form page to a simple Perl CGI script which dumps a set of static form >> data (as in the form fields are hidden and therefore no data entry is >> needed so I can just hit the submit button over and over again for >> rapid testing) to the browser. Everything runs fine, no errors on the >> server being reported, no error in the Perl script reported, just a >> blank params collection about 2% of the time, seemingly completely at >> random. Under high load and under low load there seems to be no >> difference. > > First, confirm exactly what the browser is sending when you encounter > the problem symptom: > > a) Content-Length non-zero + POST data > b) Content-Length zero > c) Content-Length non-zero but no post data (we'd expect the web > server to wait for Timeout seconds before giving up on the POST data) > > You can easily log the incoming Content-Length in the access log. =A0You > can log the incoming headers/POST data with mod_dumpio. =A0You can step > outside of the web server process itself and use a packet trace tool > such as Wireshark. =A0You can use something like the ieHttpHeaders > plug-in for IE, or equivalent for Firefox, to see the perspective of > the browser process. Ah yes, I forgot to mention I had already used Firebug and Wireshark to confirm that the browsers are correctly sending the POST data to the server 100% of the time. I'll try to look into mod_dumpio today and see if I can figure out how to use it to help trace what's going on. Thanks, - Tim Partee --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org