https://issues.apache.org/bugzilla/show_bug.cgi?id=45697
Summary: Error message incorrect "The specified module could not
be found."
Product: Apache httpd-2
Version: 2.2.8
Platform: PC
OS/Version: Windows Server 2003
Status: NEW
Keywords: ErrorMessage
Severity: normal
Priority: P3
Component: Core
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
When you use the LoadModule command in the config file to load a module whose
sharedlibrary is not compatible with the loading version of httpd it produces a
misleading error message that looks like:
httpd.exe: Syntax error on line 129 of C:/Apache2/conf/httpd.conf: Cannot
load C:/Apache2/modules/mod_auth_sspi.so into server: The specified module
could not be found.
Furthermore this error never appears in the error.log file. If you are
launching httpd via the windows Services application then you never see the
error message:(.
I consider myself an advanced technologist and I'm usually pretty quick to work
out problems like this. However, when a program as solid as httpd tells me a
file can not be found i _start_ by beleiving it. I kept thinking that maybe I
had the slashes backwords (apache reports with forward slashes when I run on
Win32 which uses back slashes), or there was a permission problem or some
attribute on the file that made it impossible for httpd to see the file.
In the end I found it was simply a matter of the module share library being
built to run with an older version of httpd.
I understand that Apache uses a magic number scheme to identify module
compatibility. Does it have to be a fatal error, then, if a module is not
compatible? Can the error messag indicate the file was incompatible with this
version of http?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
