If the module is configured, it will always show the fancy index instead of a configured index file (e.g. index.html). This affects (at least) nginx 1.11.3-r1 which is currently in portage with fancyindex 0.4.0. Upstream issue: https://github.com/aperezdc/ngx-fancyindex/issues/46 A new version containing the fix has been released: https://github.com/aperezdc/ngx-fancyindex/releases/tag/v0.4.1
Thanks for the report! I bumped the revision of the mainline version: > commit f3c2a26e1f50d245e6f06413b99f9d6102679999 > Author: Thomas Deutschmann > Date: Sat Sep 3 23:10:29 2016 +0200 > > www-servers/nginx: Revision bump to update 3rd-party modules > > - nginx-upload-progress-module v0.9.1 -> v0.9.2 > - headers-more-nginx-module v0.30 -> 0.31 > - ngx-fancyindex v0.4.0 -> v0.4.1 (bug #592464) > - lua-nginx-module v0.10.5 -> 0.10.6 > - nginx-rtmp-module v1.1.8 -> v1.1.9 > - echo-nginx-module v0.59 -> 0.60 > > Gentoo-Bug: https://bugs.gentoo.org/592464 > > Package-Manager: portage-2.3.0 ...and I also decided to bump 3rd-party modules for nginx stable (slot=0), too: > commit f03aacc3dc9a83ef1a9e89aa73eb081f0f36badf > Author: Thomas Deutschmann > Date: Sat Sep 3 23:34:08 2016 +0200 > > www-servers/nginx: Bump ebuild of stable slot to update 3rd-party modules > > Backport of commit f3c2a26e1f50d245e6f06413b99f9d6102679999 from mainline: > > - nginx-upload-progress-module v0.9.1 -> v0.9.2 > - headers-more-nginx-module v0.30 -> 0.31 > - ngx-fancyindex v0.4.0 -> v0.4.1 (bug #592464) > - lua-nginx-module v0.10.5 -> 0.10.6 > - nginx-rtmp-module v1.1.8 -> v1.1.9 > - echo-nginx-module v0.59 -> 0.60 > > Gentoo-Bug: https://bugs.gentoo.org/592464 > > Package-Manager: portage-2.3.0