1
HFS ~ HTTP File Server / HFS2.3K p4 is ready
« Last post by danny on Today at 09:01:12 PM »]HFS2.3K p4 is ready
The update is for better responsiveness.
P.S. Just in case you happen to have a custom template that requires jquery: Either you can use the "m" version that has the historic feature set (some that aren't optimal for being a file server); Or for the fast version "k", both of Leo's methods to update your jquery-reliant template, are nicer than fetching jquery out of the .exe. Then you'll be ready for when/if we get version 2.4 up to date. You can see the included "legacy template.tpl" file as an example of onboarding jquery. The new copy in my .zip file is slightly modified to include unicode fonts and a shielded archive link so that bots can't use it to archive the whole thing.
P.P.S. I have updated my router to run banip with fail2ban/debl and greensnow, so that crude ip country/range blocking is longer required.
Also, these new patched versions of HFS are hard-coded to react to HFS specific attack by banning ip, which limits experiments considerably.
The update is for better responsiveness.
P.S. Just in case you happen to have a custom template that requires jquery: Either you can use the "m" version that has the historic feature set (some that aren't optimal for being a file server); Or for the fast version "k", both of Leo's methods to update your jquery-reliant template, are nicer than fetching jquery out of the .exe. Then you'll be ready for when/if we get version 2.4 up to date. You can see the included "legacy template.tpl" file as an example of onboarding jquery. The new copy in my .zip file is slightly modified to include unicode fonts and a shielded archive link so that bots can't use it to archive the whole thing.
P.P.S. I have updated my router to run banip with fail2ban/debl and greensnow, so that crude ip country/range blocking is longer required.
Also, these new patched versions of HFS are hard-coded to react to HFS specific attack by banning ip, which limits experiments considerably.