Bug 50727 - ISAPI EXTENSION_CONTROL_BLOCK Missing PostData with .NET Client
Summary: ISAPI EXTENSION_CONTROL_BLOCK Missing PostData with .NET Client
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_isapi (show other bugs)
Version: 2.2.17
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-02-07 09:08 UTC by Maximiliano Podostroiec
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Maximiliano Podostroiec 2011-02-07 09:08:51 UTC
Using a .NET service client, like .NET WebService Studio(http://webservicestudio.codeplex.com/) the ECB is missing cbTotalBytes, cbAvailable members and lpbData points to a empty string.

This doesn't happen with a Delphi client.

Fiddler shows differently formatted XML PostData from .NET Client (Specifically XML encoding and SOAP envelopes names).

Here is an unanswered stackoverflow question with almost exact scenario(I use Delphi 2010) and apache debug logs.

Same DLL on IIS 5.1, 6 and 7 and Indy powered Debug app works like a charm with both .NET and Delphi clients.

Tried setting different values for ISAPIReadAheadBuffer which should directly affect cbAvailable member value, and enabling/disabling ISAPICacheFile directive. The result was the same.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:08 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.