Hickey, Tom wrote:
Yes this is related to a question I posted on another thread and I understand that SOAPISAP.dll is not an Apache product. But again I am trying to determine why this DLL works with version 2.2.4 and not with 2.2.14. The DLL has not changed, I am using the same DLL so something in Apache has changed. I hoped that with some additional logging I might be able to determine exactly what Apache was attempting to do when it failed.
Oh, right, that's a valid question. The "Premature end of script headers" comes from code that was written originally for CGI, but is also part of a public API and so could perfectly well be used by other code such as your .dll. Under the hood, it's caused by a function supplied by your application returning zero. That makes it hard to speculate on what could be causing it, since we know nothing about the function that returns zero. It could be one of Apache's standard functions (e.g. the one that parses a header from a CGI script), or it could be implemented within your .dll. In other words, you really do need to raise this with the supplier of your dll. Unless you can run it under a debugger yourself, in which case you should set a breakpoint at ap_scan_script_header_err_core and examine what it gets passed as the "getsfunc" argument. The one thing that concerns me from an Apache point of view is that upgrading from 2.2.x to 2.2.later-x shouldn't break your applications. Even third-party binaries, provided they use only public APIs and don't access private interfaces. So it would indeed be good to know what's changed in your case. Are you sure the configuration is identical? -- Nick Kew --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|