Activity
From 2020-11-08 to 2020-11-14
2020-11-14
- 01:54 Feature #1982: RFE: mod_redirect exact-match map: simple (non-RE) redirection
- [Title (subject) renamed to provide some scope.]
Should anyone find this and wish to try extending mod_redirect or c...
2020-11-13
- 08:51 Bug #3033: Memory Growth with PUT and full buffered streams
- (issue automatically closed with patch push)
If this issue is still unresolved, please reopen. If a new or differ... - 08:50 Bug #3033 (Fixed): Memory Growth with PUT and full buffered streams
- Applied in changeset commit:f2b33e752009065f85611a71c18ac5df94247ce7.
- 06:40 Bug #3033: Memory Growth with PUT and full buffered streams
- @flynn: I have seen clean behavior from mod_proxy as I tried to reverse-proxy a 256 MB PUT.
If I understand correc...
2020-11-12
- 22:41 Bug #3033 (Patch Pending): Memory Growth with PUT and full buffered streams
- I pushed a small patch to the tip of my dev branch @personal/gstrauss/master@. This should address the potential lar...
- 10:48 Bug #3033: Memory Growth with PUT and full buffered streams
- I applied your patch and tested three iterations with upload of 350MB, still only 5MB private dirty memory (before th...
- 10:17 Bug #3033: Memory Growth with PUT and full buffered streams
- At the very least, I need to reschedule the request once the queue to the backend clears, in the case where we have a...
- 10:07 Bug #3033: Memory Growth with PUT and full buffered streams
- I need to verify this further, as this might be an incomplete patch, but the issue appears to be in mod_fastcgi aggre...
- 09:56 Bug #3033: Memory Growth with PUT and full buffered streams
- I can reproduce the problem with your up.fcgi backend and a 900MB file upload.
I use always the current Debian pac... - 09:25 Bug #3033: Memory Growth with PUT and full buffered streams
- With larger files, I do see more memory usage, so I have something to look into and instrument. More tomorrow.
- 09:20 Bug #3033: Memory Growth with PUT and full buffered streams
- Tested my config above adding @mod_openssl@, and, separately, adding @mod_mbedtls@. Testing over TLS used more memor...
- 09:13 Bug #3033: Memory Growth with PUT and full buffered streams
- Same behaviout without TLS connection: the memory steps for each iteration are different, the memory amount after fou...
- 09:07 Bug #3033: Memory Growth with PUT and full buffered streams
- > I know at least two clients in use, which do PUT requests without Content-Length, so it is important for me.
No ... - 08:27 Bug #3033: Memory Growth with PUT and full buffered streams
- FYI: we already have had a discussion about PUT and chunked encoding, see ticket #2156. You fixed it, but only if set...
- 08:19 Bug #3033: Memory Growth with PUT and full buffered streams
- I did not change/configure ssl.read-ahead.
The connections are all over TLS, I try to make tests without ... - 08:12 Bug #3033: Memory Growth with PUT and full buffered streams
- Something is clearly wrong in lighttpd for it to use that much memory from sequential PUT requests which ought to be ...
- 07:52 Bug #3033: Memory Growth with PUT and full buffered streams
- I use big files to trigger the memory leak, currently I use a debian netinst iso image with 350MB.
The first uploa... - 06:54 Bug #3033: Memory Growth with PUT and full buffered streams
- Trying to reproduce. Unable to reproduce using basic CGI
@lighttpd.conf@...
2020-11-11
- 22:02 Bug #3033: Memory Growth with PUT and full buffered streams
- - currently I do not use valgrind
- I use the processes plugin of collectd and a self written plugin which sums up th... - 21:00 Bug #3033: Memory Growth with PUT and full buffered streams
- Does a program such as valgrind report the memory as leaked? Or are you merely seeing the lighttpd memory footprint ...
- 20:34 Bug #3033 (Fixed): Memory Growth with PUT and full buffered streams
- My memory monitoring for lighttpd shows, that some lighttpd instances leak memory.
I could track it down to PUT-re... - 19:57 Feature #3032 (Wontfix): Add a privacy option to allow IP Anonymization when creating logfiles.
- FYI: You got the response you got because you *failed* to include basic information about requirements (GDPR) with yo...
- 10:13 Feature #3032: Add a privacy option to allow IP Anonymization when creating logfiles.
- I am aware of Option 1, but I do not want to omit the IP in full.
I did not yet found a piped logger that rewrites...
2020-11-10
- 22:59 Feature #3032 (Need Feedback): Add a privacy option to allow IP Anonymization when creating logfiles.
- Why?
See [[Docs_ModAccessLog|mod_accesslog]] docs. You can already
1. define a log format which omits the IP or use... - 21:24 Feature #3032 (Wontfix): Add a privacy option to allow IP Anonymization when creating logfiles.
- With IPv4:
IP Anonymization clears the last 8 Bit of an IP Address
With IPv6:
IP Anonymization clears the last 6... - 07:33 Bug #3030: Fastcgi fails if server.tag is empty
- I didn't fix the one place you needed it! Sorry.
I applied a reverse patch from yours. - 06:32 Bug #3030: Fastcgi fails if server.tag is empty
- Thank for your quick response and fix.
Tested and works for fastcgi/php, but uwsgi is missing, see my attached patch. - 00:05 Bug #3030 (Fixed): Fastcgi fails if server.tag is empty
- Applied in changeset commit:c0e2667b714bf8be8d5cb2da44a27a25a68212be.
- 06:32 Bug #3031: uwsgi fails with HTTP/2
- Tested and works, but only with none empty server.tag, see my remark on #3030.
- 00:05 Bug #3031 (Fixed): uwsgi fails with HTTP/2
- Applied in changeset commit:169d8d3608fb90e4f00ec77d149788e59a6fc8d5.
- 00:01 Bug #3031 (Patch Pending): uwsgi fails with HTTP/2
2020-11-09
- 22:30 Bug #3031: uwsgi fails with HTTP/2
- Thanks for reporting this. This is a bug in uwsgi, but I'll think about a workaround in lighttpd.
Protocols that fo... - 14:12 Bug #3031 (Fixed): uwsgi fails with HTTP/2
- Updating to the upcoming version 1.4.56 and enabling HTTP/2 my searx instance fails with a 502.
Using strace I fou... - 22:24 Bug #3030 (Patch Pending): Fastcgi fails if server.tag is empty
- Thanks for tracking that down.
I've modified the code to accept a 0-length value with NULL ptr when creating the C... - 13:05 Bug #3030 (Fixed): Fastcgi fails if server.tag is empty
- Updating to the upcoming version 1.4.56 all my php-Script fail with a return code 400.
Reducing my setup I found,...
Also available in: Atom