| Summary: | mod_isapi always returns 500 status code | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | Christopher O'Neill <apache> |
| Component: | mod_isapi | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jochenk, rick |
| Priority: | P2 | ||
| Version: | 2.2.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Windows XP | ||
| Attachments: | the 2 patched win32 mod_isapi.so | ||
|
Description
Christopher O'Neill
2006-07-18 17:30:23 UTC
Yes this was the same bug, with different symptoms - thank you for your report. *** This bug has been marked as a duplicate of 16637 *** Sorry, for re-opening but Apaches less 2.0.55 did the correct job and I guess that since 2.0.57 the problem is re-opened due to the modifications to run mod_isapi on Unix platform. We are developer and vendor of an ISAPI extension called Active FoxPro Pages that works with Apache 2 since months but not with version later than 2.0.55 or 2.2.x - We already had correct HTTP return codes to use Redirect (302) and Authentication (401). This has been broken during last versions... We found additional forum threads related to other ISAPI extensions that report the same problems as we did with our. Apache 2.0.55 is running fine. OS: Any Windows NT based (NT4, W2K, XP, W2S3) I tested this problem with Apache 2.0.48 (OK), 2.0.55 (OK), 2.0.58 (NOT OK), 2.0.59 (NOT OK) and 2.2.3 (NOT OK). Additionally, I'd like to mention that our extension runs smoothly on other ISAPI-enabled webservers like IIS, BRS WebWeaver or Abyss. And it's IMHO no duplicate of bug 16637. For further questions either contact me - jochenk@prolib.de - or test our ISAPI extension - http://www.afpages.com/?cat=down Jochenk - it's fixed in subversion trunk, and not in the various branches (e.g. the 2.2.3 and 2.0.59). Please test http://people.apache.org/~wrowe/mod_isapi-416293.zip as cited in bug 16637 in your current 2.2.3 or 2.0.59 installation and verify if the error 500 goes away. If so your assertion that the bugs are unrelated is wrong. I stated it was "the same bug, with different symptoms". Not with the same symptoms. In any case, report back here if your issue is unexpected 500 errors, set LogLevel to debug and report back any specific messages that the 416293 flavor reports while it returns an invalid result code. If you can compare your expected results and errors to the 416293 version, we stand a better chance of resolving your bug. If your bug is -not- an unexpected 500 result from your isapi handler, then please reclose this bug asap and open a bug that describes the bug you are experiencing. Hello Will, just did some tests with the 416293 version and wget, Fiddler. The HTTP return codes are better, I get regular 200 and can produce customized ones, like 302 and 401 but... there still unexpected 500. But as you stated, I assume its best to close this entry and create a new one. *** Bug 40628 has been marked as a duplicate of this bug. *** >Please test http://people.apache.org/~wrowe/mod_isapi-416293.zip as cited
>in bug 16637 in your current 2.2.3 or 2.0.59 installation and verify if the
>error 500 goes away
Tested both 2.2.3 and 2.0.59, and both time it makes the error 500 go away.
Created attachment 18935 [details] the 2 patched win32 mod_isapi.so The patched mod_isapi.so win32 binaries for version 2.0.59 and for version 2.2.3 They are compiled with Visual C++ 2005 express edition, so the next microsoft runtime libraries are needed to run them: http://go.microsoft.com/fwlink/?linkid=65127&clcid=0x409 Comment on attachment 18935 [details]
the 2 patched win32 mod_isapi.so
Do not pollute bugzilla with binaries. You are welcome to provide an offsite
link.
|