On 8/9/2016 12:07 PM, Jacob Champion wrote:
At this point, my primary suspect is our use of recycled OVERLAPPED
structs without reinitializing them to zero. To make matters worse,
we're setting the OVERLAPPED's internal .Pointer field in the
AcceptFilter 'data' case -- which we're not supposed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roger,
On 8/24/16 9:53 AM, Roger Paanini wrote:
> Chris, I am testing it by logging into the website using basic
> authentication and then waiting for the time out duration and try
> to access the page again. I am expecting to be challenged for
> c
> I am testing it by logging into the website using basic authentication [...]
Session you are observing is browser-based, not server-based. Your browser
repeats once learned credentials in every request until it's restarted (may
depend on the browser of course). And server verifies credentials
Forgot to mention... I am using httpd as a reverse proxy. But the
downstream server has no notion of a user or sessions.
On Wed, Aug 24, 2016 at 8:53 AM, Roger Paanini
wrote:
> Chris, I am testing it by logging into the website using basic
> authentication and then waiting for the time out durat
Chris, I am testing it by logging into the website using basic
authentication and then waiting for the time out duration and try to access
the page again. I am expecting to be challenged for credentials again when
I tried to access the page after the timeout. But I am never challenged
after the tim
No Response. Please let me know if any more inputs are required.
Regards,
Amit
From: Amit Agrawal88/India/IBM@IBMIN
To: users@httpd.apache.org
Date: 08/22/2016 05:55 PM
Subject:[users@httpd] 403 Forbidden for git repository over http
Hi All,
I am trying to setup a central Gi
