ISAPIs written for MS may pass 0 as the result code with no adverse effect.

Submitted by:	Jessie Oberreuter <joberreu@moselle.com>
Reviewed by:	Will Rowe

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@89062 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/os/win32/mod_isapi.c b/src/os/win32/mod_isapi.c
index 2e00b990f799921e27a838b717b3f26d80ca93be..376c592d767b387b9e19222924c62abe99218e51 100644 (file)
--- a/src/os/win32/mod_isapi.c
+++ b/src/os/win32/mod_isapi.c
@@ -316,6 +316,7 @@ int isapi_handler (request_rec *r) {
     ap_os_dso_unload(isapi_handle);
 
     switch(retval) {
+    case 0:  /* Strange, but MS isapi accepts this as success */
     case HSE_STATUS_SUCCESS:
     case HSE_STATUS_SUCCESS_AND_KEEP_CONN:
         /* Ignore the keepalive stuff; Apache handles it just fine without