Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 70003 invoked from network); 26 Jul 2006 23:00:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Jul 2006 23:00:08 -0000 Received: (qmail 61836 invoked by uid 500); 26 Jul 2006 23:00:05 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 61511 invoked by uid 500); 26 Jul 2006 23:00:04 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 61500 invoked by uid 99); 26 Jul 2006 23:00:04 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jul 2006 16:00:04 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=RCVD_IN_NJABL_SPAM X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [207.155.248.4] (HELO repulse.cnchost.com) (207.155.248.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jul 2006 16:00:02 -0700 Received: from [192.168.0.21] (c-24-15-193-17.hsd1.il.comcast.net [24.15.193.17]) (as wrowe@rowe-clan.net) by repulse.cnchost.com (ConcentricHost(2.54) Relay) with ESMTP id 90ECA3BD3 for ; Wed, 26 Jul 2006 18:59:35 -0400 (EDT) Message-ID: <44C7F3A4.50000@rowe-clan.net> Date: Wed, 26 Jul 2006 17:58:44 -0500 From: "William A. Rowe, Jr." User-Agent: Thunderbird 1.5.0.4 (X11/20060614) MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: mod_isapi randomly produces corrupt output References: <44BE9D0E.8050204@chrisoneill.co.uk> In-Reply-To: <44BE9D0E.8050204@chrisoneill.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Chris, are you setting the FakeAsync flag, and if you do, does this solve it or change the behavior? http://httpd.apache.org/docs/trunk/mod/mod_isapi.html#isapifakeasync Note several MS examples abuse the CID (connection context) and don't set it, and apparently MS no longer inspects it. But we do, and violating it will lead to death of the app. Bill Christopher O'Neill wrote: > /This email was originally sent to William A. Rowe, he suggested that I > resend it to this list:/ > > Hi Bill, > > I'm currently in the process of ensuring a web app that I have developed > for IIS works correctly with Apache's mod_isapi. After stumbling upon > an error which caused a 500 status code to be returned on every (valid) > request, I managed to find your updated module and installed it - > eliminating this problem. > > However, I have noticed a different problem: Every so often a corrupt > page will be generated (this seems to occur at random intervals - with > about10% probability I would guess). For instance, using the HelloISAPI > example file from Microsoft's platform SDK (binary & source attached): > > Expected output: > > > > HelloIsapi Sample Extension > >

Hello ISAPI!

> This is a very simple ISAPI extension. > > > Unexpected output: > > > > 200 OK > >

OK

The server encountered an internal error or > misconfiguration and was unable to complete > your request.

Please contact the server administrator, > admin@local and inform them of the time the error occurred, > and anything you might have done that may have > caused the error.

More information about this error may be available > in the server error log.

> > HTTP/1.1 200 OK > Date: Tue, 18 Jul 2006 22:39:08 GMT > Server: Apache/2.2.2 (Win32) > Content-Length: 140 > Keep-Alive: timeout=5, max=91 > Connection: Keep-Alive > Content-Type: text/html > > > > > HelloIsapi Sample Extension > >

Hello ISAPI!

> This is a very simple ISAPI extension. > > 200 OK > >

OK

The server encountered an internal error or > misconfiguration and was unable to complete > your request.

> >

Please contact the server administrator, > admin@local and inform them of the time the error occurred, > and anything you might have done that may have > caused the error.

More information about this error may be available > in the server error log.

> > > > As you can see, the real output seems to be wrapped inside an error > response. The next refresh after this error is also a lot slower than > normal (perhaps the .dll is being reloaded?). This was tested by > hitting reload at a rate of about 1 per second until the error page was > displayed. > > I didn't notice this bug with the original version of mod_isapi, > unfortunately I overwrote the original with your updated version so am > unable to test. > > Anyway, I hope this is useful.. > > > - Chris