Recent Posts

Pages: [1] 2 3 ... 10
Everything else / Merry cristms
« Last post by Fysack on Today at 01:20:23 AM »
Brotthers! Best ever. Hang in there <3
so good to see that te world still alive. Yea. That Stevens guy
HFS ~ HTTP File Server / Re: Version 2.3k missing on sourceforge
« Last post by Fysack on Today at 01:12:59 AM »
safe as hell. Best crew ever
HTML & templates / Re: Chat for HFS.
« Last post by Fysack on Today at 01:09:00 AM »
ayatollas of rock`n`rollas
HFS ~ HTTP File Server / Re: ban on the run
« Last post by Fysack on Today at 01:06:50 AM »
hardcore *muselarm*
Beta / Re: version 2.4
« Last post by Fysack on Today at 01:01:47 AM »
Beta / Re: version 2.4
« Last post by Fysack on Today at 12:36:01 AM »
HFS ~ HTTP File Server / Re: HFS behind Nginx reverse proxy
« Last post by stanleydoss2018 on December 13, 2018, 09:03:22 AM »
i guess you should rewrite the url, removing the /hfs when the request is passed to hfs.
google for it. in Apache rewrite is possible.

worst case you can move all your stuff in the hfs' virtual file system under a folder /hfs.

Yes, Apache rewrite: would be probably the easiest solution here.
HFS ~ HTTP File Server / Re: ban on the run
« Last post by Mars on December 10, 2018, 09:02:39 AM »
if it is necessary to send the addition of a ban ip remotely, it must be sended a form to an hfs script that will support the addition of the value using the macro {.set ini | .} but it is delicate from a safe point of view

you must retrieve the set using {.get ini | ban-list.}
but the data in return are in the form| allowed| # NO!|

including pipes and making the management pretty tricky because of the macros.

it is probably necessary to use these macros, but I do not know the exact effects in the handling of text strings

     'no pipe'        replace '|'  by '{:|:}'
     'no pipe'        replace '{:|:}'  by '|'

the fields must be separated and then reassembled to be fed back into the configuration, which will have to be saved automatically at the output or at regular intervals or in force by means of a macro.
everything that includes remote hfs configuration management is a risk for hacking, especially when the exchanges are not done in SSL

it must be remembered that mishandling or erroneous data may create a ban rendering hfs unreachable

I do not know if there is an equivalent in English but as we say in France, "the game is not worth the candle"
Pages: [1] 2 3 ... 10