Re: [users@httpd] httpd on Debian

Thanks Alex. I think that I configured the webdav correctly, since after a lot of huffs and puffs, I could get /etc/init.d/apache2 restart working correctly on the Debian server machine. But then, I tried (on the Debian webdav server machine) ::

Re: [users@httpd] httpd on Debian

--On 5 September 2012 11:57:00 +0530 Ajay Garg ajaygargn...@gmail.com wrote: Does that mean that the webdav is still not properly configured/started? Or it could be a false negative? It means nothing is listening on port 443 of your localhost address. That does not preclude it listening

Re: [users@httpd] httpd on Debian

Alex, this is the output, when I run the command apache2ctl -S on my Debian VM (guest machine), hosted on a Fedora-14 machine :: ### VirtualHost configuration: wildcard NameVirtualHosts and _default_ servers: *:443

Re: [users@httpd] httpd on Debian

this is the output, when I run the command apache2ctl -S on my Debian VM (guest machine), hosted on a Fedora-14 machine :: ### VirtualHost configuration: wildcard NameVirtualHosts and _default_ servers: *:443 

[users@httpd] Problem in configuring WebDAV on Debian Squeeze

Hi all. I have been able to setup WebDAV sharing on a server hosted on Fedora-14 and Fedora-17. However, when I try to do the same on a Debian Squeeze, I am unsuccessful. Here is the relevant info that I think is important :: === SETUP === * Debian Squeeze is installed as a VM, on a

[users@httpd] What verification does Apache do as part of SSLVerifyClient?

All, I'm starting to use SSLVerifyClient. I can't find any documentation on exactly what it means to verify a client, however. By reading the source, I found that some of the work is delegated to OpenSSL and its behavior is somewhat documented here:

Re: [users@httpd] What verification does Apache do as part of SSLVerifyClient?

On September 5, 2012 16:32 , john.e.gr...@wellsfargo.com wrote: I’m starting to use SSLVerifyClient. I can’t find any documentation on exactly what it means to verify a client, however. By reading the source, I found that some of the work is delegated to OpenSSL and its behavior is somewhat

[users@httpd] URL Requests being use to probe my server

CentOS 6, Apache/2.2.15 (Unix) I am receiving messages in my Logwatch that state: A total of 1 sites probed the server 210.86.231.xx A total of 1 possible successful probes were detected (the following URLs contain strings that match one or more of a listing of strings that indicate a

Re: [users@httpd] URL Requests being use to probe my server

On Wed, Sep 5, 2012 at 6:45 PM, Jason T. Slack-Moehrle slackmoeh...@gmail.com wrote: CentOS 6, Apache/2.2.15 (Unix) I am receiving messages in my Logwatch that state: A total of 1 sites probed the server 210.86.231.xx A total of 1 possible successful probes were detected (the

[users@httpd] Problems with enabling LDAP support in version 2.4.3

I unpacked the httpd archive, added apr-1.4.6, and apr-util-1.4.1 to the srclib directory under apr and apr-util and ran ./configure --prefix=/usr/local/apache2 --enable-authnz-ldap --enable-ldap --with-included-apr. The following is displayed. I have read some awful posts with solutions to

Re: [users@httpd] Problems with enabling LDAP support in version 2.4.3

On Wed, Sep 5, 2012 at 8:11 PM, Muzinich, Mike muzi...@losrios.edu wrote: I unpacked the httpd archive, added apr-1.4.6, and apr-util-1.4.1 to the srclib directory under apr and apr-util and ran ./configure --prefix=/usr/local/apache2 --enable-authnz-ldap --enable-ldap --with-included-apr.

Re: [users@httpd] Problems with enabling LDAP support in version 2.4.3

Thanks. That resolved the problem. It sure would be nice if Apache would put that option in the help output. ./configure --help | grep ldap --enable-authnz-ldapLDAP based authentication --enable-ldap LDAP caching and connection pooling services Mike Muzinich Network Security