Re: [users@httpd] apache 2.4 directory autoindex corrupted

Jan Schaumann <jscha...@netmeister.org> wrote: > Hmmm. This is apache-2.4.16 from NetBSD pkgsrc; I've tried both a > binary package provided by NetBSD as well as a locally compiled pkgsrc > version. Just to close the loop (albeit unsatisfactory): my system was due for an OS

Re: [users@httpd] Re: apache 2.4 directory autoindex corrupted

Kurtis Rader wrote: > My first guess is that you've enabled memory-mapping of content. See the > EnableMMAP directive: > http://httpd.apache.org/docs/current/mod/core.html#enablemmap Correct. And turning that off does avoid sending the null bytes, but the problem remains

Re: [users@httpd] apache 2.4 directory autoindex corrupted

Eric Covener wrote: > Pretty odd, can you strace/truss and see what comes back for readdir/stat/??? I see just what it sounded like: httpd tries to mmap a much larger file than it actually has: 1878 27 httpdCALL __stat50(0x7f7ff7bb16f0,0x7f7fecbff780) 1878

[users@httpd] Re: apache 2.4 directory autoindex corrupted

Jan Schaumann <jscha...@netmeister.org> wrote: > I just upgraded apache 2.2 to apache 2.4. After the upgrade, my > autoindex directory listings show up as corrupted strings (see > https://www.netmeister.org/t/ for an example). All other content > serving appears to work fin

[users@httpd] apache 2.4 directory autoindex corrupted

Hello, I just upgraded apache 2.2 to apache 2.4. After the upgrade, my autoindex directory listings show up as corrupted strings (see https://www.netmeister.org/t/ for an example). All other content serving appears to work fine. If you happen to know the file/dir names, you can successfully