You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In light of #17 I tried to use ngx_echo to make it include README.txt, but I failed miserably.
Using 0.4.1 on nginx 1.10, any call to echo_location_async or similar from within a page generated by fancyindex rapidly eats all available memory until it crashes my machine.
Accessing the faux location directly (not through fancy index) properly includes the file I want.
In the example above, accessing /any-dir/ crashes the server, whereas accessing /HEADER.html, which isn't handled by fancyindex, renders the page as expected.
FWIW here's directory tree for the example above:
/
srv/
www/
xxxxx/
any-dir/
file1.txt
file2.txt
index.txt
HEADER.html (not a physical file)
The text was updated successfully, but these errors were encountered:
In light of #17 I tried to use
ngx_echo
to make it includeREADME.txt
, but I failed miserably.Using 0.4.1 on nginx 1.10, any call to
echo_location_async
or similar from within a page generated by fancyindex rapidly eats all available memory until it crashes my machine.Accessing the faux location directly (not through fancy index) properly includes the file I want.
Configuration:
In the example above, accessing
/any-dir/
crashes the server, whereas accessing/HEADER.html
, which isn't handled by fancyindex, renders the page as expected.FWIW here's directory tree for the example above:
/
srv/
www/
xxxxx/
any-dir/
file1.txt
file2.txt
index.txt
HEADER.html
(not a physical file)The text was updated successfully, but these errors were encountered: