Message-ID: <33D51FB0.F6ACA3F2@algroup.co.uk>
Date: Tue, 22 Jul 1997 22:01:36 +0100
From: Ben Laurie <ben@algroup.co.uk>
Organization: A.L. Digital Ltd.
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: cvs commit: apache/src/nt mod_isapi.c modules.c
References: <Pine.GSO.3.95.970722134736.15981A-100000@veal.organic.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Alexei Kosut wrote:
> 
> On Tue, 22 Jul 1997, Ben Laurie wrote:
> 
> > >   Add nt/mod_isapi.c, which implements most of the ISAPI Extension 2.0
> > >   specification. It has a temporary cap of the input buffer at 48k,
> > >   until a better solution can be found.
> >
> > I haven't quite understood what the problem is, exactly. Could you
> > explain?
> 
> Sure. The ISAPI specification says that the server should read in some
> chunk (IIS uses 48k, and the spec mandates 48k or larger) of the client
> data, and store it in a buffer in the structure passed to the ISA. If
> there's more than that, the ISA can call ReadClient() to get the rest of
> the data. However, IIS doesn't follow the ISAPI spec in a way that makes
> it so I can't do this. The only way I could figure out how to it work
> with both the ISAPI spec and with existing ISAs is to read in the entire
> request entity, and store it in the structure.

In what way does IIS not follow the ISAPI spec?

Cheers,

Ben.

-- 
Ben Laurie                Phone: +44 (181) 994 6435  Email:
ben@algroup.co.uk
Freelance Consultant and  Fax:   +44 (181) 994 6472
Technical Director        URL: http://www.algroup.co.uk/Apache-SSL
A.L. Digital Ltd,         Apache Group member (http://www.apache.org)
London, England.          Apache-SSL author