[users@httpd] apache 2.4 email autoconfig and autodiscover configuration

2018-04-19 Thread David Mehler
Hello, If anyone is using email autoconfig and/or email autodiscover with apache 2.4 can you let me know? I'm trying to get it working, and the xml files from what i'm researching on the net, look good. I'd like to know your apache configuration? Thanks. Dave. ---

[users@httpd] Re: Apache supports client initiated renegotiation

2018-04-19 Thread Hemant Chaudhary
Hi All, Any help on this issue. My openssl is sending Secure client initiated renegotiation but my apache server is rejecting because it is client initiated. I checked custom log and it shows my apache supports secure renegotiation. Can somebody has tried secure renegotiation in apache. How to

Re: [users@httpd] Logging in apache

2018-04-19 Thread Rainer Canavan
On Wed, Apr 18, 2018 at 9:29 PM, Eric Covener wrote: > On Wed, Apr 18, 2018 at 3:18 PM, Hemant Chaudhary > wrote: >> Thanks Eric >> >> It means thread are using lock so that one thread/process can write a time. > I believe it's unlocked, I think posix promises they will not be > interleaved if wr

Re: [users@httpd] Logging in apache

2018-04-19 Thread Eric Covener
On Thu, Apr 19, 2018 at 8:36 AM, Rainer Canavan wrote: > On Wed, Apr 18, 2018 at 9:29 PM, Eric Covener wrote: >> On Wed, Apr 18, 2018 at 3:18 PM, Hemant Chaudhary >> wrote: >>> Thanks Eric >>> >>> It means thread are using lock so that one thread/process can write a time. >> I believe it's unloc

[users@httpd] mod_ratelimit working by steps ?

2018-04-19 Thread nerbrume
Hello all, I'm using Apache 2.4.24 on Debian 9 Stable, behind a DSL connection, with an estimated upload capacity of ~130kB/s. I'm trying to limit the bandwidth available to my users (per-connection limit is fine). However, it seems to me that the rate-limit parameter is coarsely grained : -

[users@httpd] Apache supports client initiated renegotiation

2018-04-19 Thread Hemant Chaudhary
Hi Team, I tried to send request from openssl-1.0.2d to Apache server-2.4.25 for ssl renegotiation using command "openssl s_client -connect IP:PORT". I got error RENEGOTIATING 2283136:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:s3_pkt.c:656. I checked in error log, error is

[users@httpd] Server Configuration

2018-04-19 Thread Anshuk Pal Chaudhuri
Need your suggestion on setting up an web application and REST api in server. Currently there are 3 applications like as below 1. User web application - Running on node.js - port 3389 / universal react application 2. Admin web application - Running on apache - port 8080 / laravel 3. Rest Api for