bendem
bendem
#163 fixed this, but it's neither in 1.2.6.3 nor 1.2.6.4. You can use d15bd2d if you want this fixed.
Because the [VERSION](https://github.com/leenooks/phpLDAPadmin/blob/BRANCH-1.2/VERSION) file was not updated before tagging.
Hi there, I just found this issue and I think my problem fits the current discussion. Many of our queries are built build joining our tables to ```sql from generate_series(...
That would be the keepalive setting. You really want to close the connection after sending the response to have a consistent behavior in browsers: ``` -N shutdown(2) the network socket...
You should set it to `close`, not remove it. Otherwise it means you are accepting the browser's setting which is `keep-alive`.
Sorry, I realise I had removed it in my example, added it back.
> wouldn't you want Connection:keep-alive to give a hint to the clients that they need to close the connection because the server won't? Actually, adding `keep-alive` tells the client to...
> Have you tried that yet? When I tried making that change it didn't seem to make a difference with Chrome or Firefox. I have not, but I have read...
Yep, that fixes it on fedora as well: `sudo ln -s /usr/lib64/libudev.so.1 /usr/lib64/libudev.so.0` `yum provides libudev.so.0` doesn't seem to find packages providing it so I guess that's a way to...
> I meant to add but forgot: although it is not a perfect solution, the high potential for leaking sensitive information is why we recommend to set up [authentication in...