Re: [users@httpd] Followup to [Bug 50028] (LDAP authentication with encrypted passwords)
On Sat, 2013-03-30 at 13:51 -0400, Stormy wrote: > At 12:05 PM 3/30/2013 +1000, Noel Butler wrote: > > > Sounds like a package manager problem to me > > > I'm not sure of that, but I'm not a php expert :( Just been doing > some testing on the sandbox (dpkg --force-all, not apt), and it comes > back to php lack of thread safety. Blowfish encryptation doesn't > function without full php and > > libapache2-mod-php5, and if I leave Uhg, yeah, but this is because the way your operating system distro vendor has packaged these softwares. libapache2-mod-php5 is not an official package name Try getting httpd and php sources and build them, its why I wont touch things like that from certain distros, too much butchering goes on. php has a helpful mailing list for php related questions, but AFAIK, php is thread safe, but not all modules might be, again, a question for them as its not httpd related. > th > > ose in place and go back to mpm-worker (faster, less overhead for my > server usage) I seem to be in trouble with env vars (setlocale.php). > Not sure if I can run FastCGI and remove mod-php? I've read that this > would restore thread safety by > > taking php outside Apache (2.2.22 on U 12.04 LTS) > > > By the way, is there a "quick" way of swapping between worker and > prefork without re-compiling? That would make my testing a whole lot > easier. > httpd -l and look to see whats there I am using only 2.4 now, event (similar, but advanced to, worker) is now the default MPM, if you want prefork compile with --with-mpm=prefork signature.asc Description: This is a digitally signed message part
[users@httpd] Apache fails to start when Xerces library is used in a C++ module
Hello,
I have written a C++ module to invoke the Xerces C++ XML library to parse a
XML file. I'm unable to start httpd.exe with these changes. Here are the
details -
a) Apache server version: httpd-2.4.4-win64
b) Xerces version: xerces-c-3.1.1-x86_64-windows-vc-10.0
c) Development envt: Visual Studio 2010 with SP1
Following are the settings I have made in Visual Studio so that the C++
module refers to the Xerces library:
1. Additional Include Directories =
E:\xerces-c-3.1.1-x86_64-windows-vc-10.0\xerces-c-3.1.1-x86_64-windows-vc-10.0\include
2. Additional Dependencies = xerces-c_3.lib and xerces-c_static_3.lib
3. Additional library directories =
E:\xerces-c-3.1.1-x86_64-windows-vc-10.0\xerces-c-3.1.1-x86_64-windows-vc-10.0\lib
4. Debugging -> Environment:
PATH=E:\xerces-c-3.1.1-x86_64-windows-vc-10.0\xerces-c-3.1.1-x86_64-windows-vc-10.0\bin
5. In the Operating System environment variables, added the path
E:\xerces-c-3.1.1-x86_64-windows-vc-10.0\xerces-c-3.1.1-x86_64-windows-vc-10.0\bin
to the environment variable PATH
6. The code in my C++ module to invoke the Xerces library routine goes like
this -
try {
XMLPlatformUtils::Initialize(); // Initialize Xerces infrastructure
}
catch( XMLException& e ) {
char* message = XMLString::transcode( e.getMessage() );
XMLString::release( &message );
}
XMLPlatformUtils::Terminate();
7. Added the below in httpd.conf file -
LoadModule filter_module modules/XercesDLL.dll
AddOutputFilterByType TagFilter text/html text/plain text/css
8. If i try to launch httpd.exe from command prompt, I see the below error -
>httpd.exe
*httpd.exe: Syntax error on line 172 of
E:/httpd-2.4.4-win64/Apache24/conf/httpd.conf: Cannot load
modules/XercesDLL.dll into server: T*
*he specified module could not be found.*
Even if I comment out the above C++ code in step 6, Apache still fails to
start. That means Apache is failing to load the Xerces library version
I'm using, irrespective of the way I'm invoking the library.
However, If I write a standalone DLL that invokes the above Xerces library
version, and invoke this DLL from an EXE then I'm successfully able to
parse the XML. This means, the Xerces library fails to get loaded only by
the Apache server for some reason.
I think its got something to do with the C to C++ linkage, not sure tho.
Any help is highly apreciated.
Thanks.
[users@httpd] standard shutdown error apache mod_ossl
Hi, We are facing very weird problem for one of our website. We are able to access the problematic website using https protocol on Desktop machines as well as on Android 2.X OS. We are seeing network error when we are hitting the same URL from Android 4.X OS. After enabling the debug logs, we are seeing following entries in the ssl_engine_log [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed with standard shutdown (server hostname:443, client x.x.x.x) Need to understand why it is only happening with Android 4.X version OS. Also what is the meaning of standard shutdown and how to debug it further. Environment information is as follows OS: Solaris 5.10 64 bit WebServer Version : Apache 1.3.31 Following is the VirtualHost entries fyr: SSLEngine On SSLProtocol +ALL -SSLv2 SSLCipherSuite HIGH:MEDIUM SSLWallet file:/default Regards, Vidyadhar - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] standard shutdown error apache mod_ossl
On 31/03/2013 9:41 PM, "Techienote com" wrote: > > Hi, > > We are facing very weird problem for one of our website. We are able > to access the problematic website using https protocol on Desktop > machines as well as on Android 2.X OS. We are seeing network error > when we are hitting the same URL from Android 4.X OS. > > After enabling the debug logs, we are seeing following entries in the > ssl_engine_log > > [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed with > standard shutdown (server hostname:443, client x.x.x.x) > This is info not a error > Need to understand why it is only happening with Android 4.X version > OS. Also what is the meaning of standard shutdown and how to debug it > further. > > Environment information is as follows > OS: Solaris 5.10 64 bit > WebServer Version : Apache 1.3.31 > Are you seriously still running apache 1? > Following is the VirtualHost entries fyr: > > SSLEngine On > SSLProtocol +ALL -SSLv2 > SSLCipherSuite HIGH:MEDIUM > SSLWallet file:/default > > > Regards, > Vidyadhar > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org >
Re: [users@httpd] standard shutdown error apache mod_ossl
Hi Igor, On 3/31/13, Igor Cicimov wrote: > On 31/03/2013 9:41 PM, "Techienote com" wrote: >> >> Hi, >> >> We are facing very weird problem for one of our website. We are able >> to access the problematic website using https protocol on Desktop >> machines as well as on Android 2.X OS. We are seeing network error >> when we are hitting the same URL from Android 4.X OS. >> >> After enabling the debug logs, we are seeing following entries in the >> ssl_engine_log >> >> [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed with >> standard shutdown (server hostname:443, client x.x.x.x) >> > This is info not a error This is the only entry which we are seeing at the time of issue. > >> Need to understand why it is only happening with Android 4.X version >> OS. Also what is the meaning of standard shutdown and how to debug it >> further. >> >> Environment information is as follows >> OS: Solaris 5.10 64 bit >> WebServer Version : Apache 1.3.31 >> > Are you seriously still running apache 1? Yes Is there any further way to debug this? > >> Following is the VirtualHost entries fyr: >> >> SSLEngine On >> SSLProtocol +ALL -SSLv2 >> SSLCipherSuite HIGH:MEDIUM >> SSLWallet file:/default >> Regards, Vidyadhar - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] standard shutdown error apache mod_ossl
Hi Richard, >> >> >> Original Message >>> Date: Sunday, March 31, 2013 04:10:57 PM +0530 >>> From: Techienote com >>> To: users@httpd.apache.org >>> Cc: >>> Subject: [users@httpd] standard shutdown error apache mod_ossl >>> >>> Hi, >>> >>> We are facing very weird problem for one of our website. We are >>> able to access the problematic website using https protocol on >>> Desktop machines as well as on Android 2.X OS. We are seeing >>> network error when we are hitting the same URL from Android 4.X OS. >>> >>> After enabling the debug logs, we are seeing following entries in >>> the ssl_engine_log >>> >>> [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed >>> with standard shutdown (server hostname:443, client x.x.x.x) >>> >>> Need to understand why it is only happening with Android 4.X >>> version OS. Also what is the meaning of standard shutdown and how >>> to debug it further. >>> >>> Environment information is as follows >>> OS: Solaris 5.10 64 bit >>> WebServer Version : Apache 1.3.31 >>> >>> Following is the VirtualHost entries fyr: >>> >>> SSLEngine On >>> SSLProtocol +ALL -SSLv2 >>> SSLCipherSuite HIGH:MEDIUM >>> SSLWallet file:/default >>> >>> >> >> Are you using a self-signed cert on the server side? If so, are you >> getting the standard "trust" warnings with the android-4.x browser? It is a CA signed certificate. >> >> I'm assuming you're using the default browser on the android-4.x >> device -- have you tried others -- firefox, chrome, dolphin (there >> are also beta versions of ff and chrome available) -- to see if you >> get a different interaction? [i don't have an SSL site to try things >> against at the moment.] Site is working fine in Opera and Firefox. It is not working with default browser and in chrome. >> >> - Richard >> >> >> >> >> Regards, Vidyadhar - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] standard shutdown error apache mod_ossl
On 31/03/2013 10:02 PM, "Techienote com" wrote: > > Hi Igor, > > On 3/31/13, Igor Cicimov wrote: > > On 31/03/2013 9:41 PM, "Techienote com" wrote: > >> > >> Hi, > >> > >> We are facing very weird problem for one of our website. We are able > >> to access the problematic website using https protocol on Desktop > >> machines as well as on Android 2.X OS. We are seeing network error > >> when we are hitting the same URL from Android 4.X OS. > >> > >> After enabling the debug logs, we are seeing following entries in the > >> ssl_engine_log > >> > >> [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed with > >> standard shutdown (server hostname:443, client x.x.x.x) > >> > > This is info not a error > This is the only entry which we are seeing at the time of issue. > > > >> Need to understand why it is only happening with Android 4.X version > >> OS. Also what is the meaning of standard shutdown and how to debug it > >> further. > >> > >> Environment information is as follows > >> OS: Solaris 5.10 64 bit > >> WebServer Version : Apache 1.3.31 > >> > > Are you seriously still running apache 1? > Yes > Is there any further way to debug this? > > Put LogLevel debug inside https host. Have you tried different browsers? > >> Following is the VirtualHost entries fyr: > >> > >> SSLEngine On > >> SSLProtocol +ALL -SSLv2 > >> SSLCipherSuite HIGH:MEDIUM > >> SSLWallet file:/default > >> > > Regards, > Vidyadhar > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org >
Re: [users@httpd] standard shutdown error apache mod_ossl
Hi Igor, On 3/31/13, Igor Cicimov wrote: > On 31/03/2013 10:02 PM, "Techienote com" wrote: >> >> Hi Igor, >> >> On 3/31/13, Igor Cicimov wrote: >> > On 31/03/2013 9:41 PM, "Techienote com" > wrote: >> >> >> >> Hi, >> >> >> >> We are facing very weird problem for one of our website. We are able >> >> to access the problematic website using https protocol on Desktop >> >> machines as well as on Android 2.X OS. We are seeing network error >> >> when we are hitting the same URL from Android 4.X OS. >> >> >> >> After enabling the debug logs, we are seeing following entries in the >> >> ssl_engine_log >> >> >> >> [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed with >> >> standard shutdown (server hostname:443, client x.x.x.x) >> >> >> > This is info not a error >> This is the only entry which we are seeing at the time of issue. >> > >> >> Need to understand why it is only happening with Android 4.X version >> >> OS. Also what is the meaning of standard shutdown and how to debug it >> >> further. >> >> >> >> Environment information is as follows >> >> OS: Solaris 5.10 64 bit >> >> WebServer Version : Apache 1.3.31 >> >> >> > Are you seriously still running apache 1? >> Yes >> Is there any further way to debug this? >> > > Put > LogLevel debug > inside https host. The above log entries we are seeing after enabling the debug log > Have you tried different browsers? Working fine in firefox and opera. Only problem with default browser and google chrome. >> >> Following is the VirtualHost entries fyr: >> >> >> >> SSLEngine On >> >> SSLProtocol +ALL -SSLv2 >> >> SSLCipherSuite HIGH:MEDIUM >> >> SSLWallet file:/default >> >> >> >> Regards, >> Vidyadhar >> >> - >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >> > - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] standard shutdown error apache mod_ossl
On 31/03/2013 10:09 PM, "Igor Cicimov" wrote: > > > On 31/03/2013 10:02 PM, "Techienote com" wrote: > > > > Hi Igor, > > > > On 3/31/13, Igor Cicimov wrote: > > > On 31/03/2013 9:41 PM, "Techienote com" wrote: > > >> > > >> Hi, > > >> > > >> We are facing very weird problem for one of our website. We are able > > >> to access the problematic website using https protocol on Desktop > > >> machines as well as on Android 2.X OS. We are seeing network error > > >> when we are hitting the same URL from Android 4.X OS. > > >> > > >> After enabling the debug logs, we are seeing following entries in the > > >> ssl_engine_log > > >> > > >> [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed with > > >> standard shutdown (server hostname:443, client x.x.x.x) > > >> > > > This is info not a error > > This is the only entry which we are seeing at the time of issue. > > > > > >> Need to understand why it is only happening with Android 4.X version > > >> OS. Also what is the meaning of standard shutdown and how to debug it > > >> further. > > >> > > >> Environment information is as follows > > >> OS: Solaris 5.10 64 bit > > >> WebServer Version : Apache 1.3.31 > > >> > > > Are you seriously still running apache 1? > > Yes > > Is there any further way to debug this? > > > > Put > LogLevel debug > inside https host. > Have you tried different browsers? > Also start snoop on port 443 and check what is going on. > > >> Following is the VirtualHost entries fyr: > > >> > > >> SSLEngine On > > >> SSLProtocol +ALL -SSLv2 > > >> SSLCipherSuite HIGH:MEDIUM > > >> SSLWallet file:/default > > >> > > > > Regards, > > Vidyadhar > > > > - > > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > > For additional commands, e-mail: users-h...@httpd.apache.org > >
Re: [users@httpd] standard shutdown error apache mod_ossl
On 3/31/13, Igor Cicimov wrote: > On 31/03/2013 10:09 PM, "Igor Cicimov" wrote: >> >> >> On 31/03/2013 10:02 PM, "Techienote com" >> wrote: >> > >> > Hi Igor, >> > >> > On 3/31/13, Igor Cicimov wrote: >> > > On 31/03/2013 9:41 PM, "Techienote com" > wrote: >> > >> >> > >> Hi, >> > >> >> > >> We are facing very weird problem for one of our website. We are able >> > >> to access the problematic website using https protocol on Desktop >> > >> machines as well as on Android 2.X OS. We are seeing network error >> > >> when we are hitting the same URL from Android 4.X OS. >> > >> >> > >> After enabling the debug logs, we are seeing following entries in >> > >> the >> > >> ssl_engine_log >> > >> >> > >> [31/Mar/2013 15:41:58 26881] [info] Connection to child 2 closed >> > >> with >> > >> standard shutdown (server hostname:443, client x.x.x.x) >> > >> >> > > This is info not a error >> > This is the only entry which we are seeing at the time of issue. >> > > >> > >> Need to understand why it is only happening with Android 4.X version >> > >> OS. Also what is the meaning of standard shutdown and how to debug >> > >> it >> > >> further. >> > >> >> > >> Environment information is as follows >> > >> OS: Solaris 5.10 64 bit >> > >> WebServer Version : Apache 1.3.31 >> > >> >> > > Are you seriously still running apache 1? >> > Yes >> > Is there any further way to debug this? >> > > >> Put >> LogLevel debug >> inside https host. >> Have you tried different browsers? >> > Also start snoop on port 443 and check what is going on. Did you mean sniff. If no kindly let me know how to snoop on port 443. > >> > >> Following is the VirtualHost entries fyr: >> > >> >> > >> SSLEngine On >> > >> SSLProtocol +ALL -SSLv2 >> > >> SSLCipherSuite HIGH:MEDIUM >> > >> SSLWallet file:/default >> > >> >> > >> > Regards, >> > Vidyadhar >> > >> > - >> > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> > For additional commands, e-mail: users-h...@httpd.apache.org >> > > - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
