Here's a packet-capture: http://imgur.com/a/53iL9
I was wrong about this being browser-side. Now that I've tested via HTTP and watched with Wireshark, I can see the client-side issues a POST, and waits a long time for the server's 200 OK response. (took 130 seconds... ugggh) What can I do from the server-side to determine where the holdup is? I'd be happy to provide any logs that would help. All other LDAP operations from PHP sites I host work great, so it seems to be isolated to this. Thanks On Wed, Feb 8, 2017 at 8:58 AM, Clément OUDOT < clement.ou...@savoirfairelinux.com> wrote: > > > Le 08/02/2017 à 15:51, jdelisle a écrit : > >> All other PHP-based applications work great. Again, I really don't think >> the issue is happening server-side, it appears to be the browser doing >> *something*, but I have no idea what or how to provide more info about >> what's happening. >> >> I can move the site to HTTP and provide packet captures during a >> password-reset of a test account, if that helps. >> > > Any log/capture can help to understand your problem. You can also use your > browser devtools to see how requests are sent and analyze what took so long > (DNS, SSL, etc.) > > > > Clément. > > _______________________________________________ > ltb-users mailing list > ltb-users@lists.ltb-project.org > http://lists.ltb-project.org/listinfo/ltb-users >
_______________________________________________ ltb-users mailing list ltb-users@lists.ltb-project.org http://lists.ltb-project.org/listinfo/ltb-users
