rejetto forum

Recent Posts

11
Programmers corner / Re: Ways to trigger events at a specific file download/ request
« Last post by rejetto on January 24, 2022, 04:48:21 PM »
hi, and welcome!
the idea is that inside the [whatever] you can decide your action based on the url. For example

[request]
{.if|{.pos|/asd|%url%.}|{:{.disconnect.}:}.}



this disconnects, but you can do something else
12
Programmers corner / Ways to trigger events at a specific file download/ request
« Last post by Fenn on January 24, 2022, 10:22:52 AM »
I'm trying to figure out a way to run a specific script by form of [request] or [download] but not any download or request but if a specific directory/ file is accessed.
i have looked though a bunch of threads and i could never find highly detailed information or a manual to use the hfs.events file
if anyone has done this please help
Thanks
13
at the moment i'm very busy with hfs3 and hate to work on previous version, because it's very old stuff that's hard to deal with.
i cannot exclude doing some work with it in the future.

stand-alone exe, sure. it's already so.

it's not yet user-friendly, right, but it's still easier than apache.
right now i started working on the administration interface, the equivalent of the hfs2 main window. This alone will take me tens of hours of work.
14
good news, but hfs3 is still a long way from being user-friendly, right? any chance of a hfs2 fix?

and while we're on the topic of hfs3, will hfs3 support a single stand-alone exe file like hfs2?
15
sorry for the bug.
i just verified that hfs 3 (next) works correctly with this case
16
Bug reports / Re: HFS external IP not working
« Last post by rejetto on January 23, 2022, 02:14:09 PM »
try disabling windows firewall temporarily
17
HFS ~ HTTP File Server / Re: a new beginning...
« Last post by rejetto on January 23, 2022, 02:12:10 PM »
https://github.com/rejetto/hfs/releases/tag/v0.8.0
pagination will allow you to work even with 30k files long lists
forbid listing of a specific folder
button to invert selection
18
Bug reports / Re: HFS external IP not working
« Last post by hanshenrik on January 22, 2022, 12:06:31 PM »
sounds like a port-forwarding issue, not a HFS bug.. are you familiar with port-forwarding? if not, maybe try a guide like https://www.hellotech.com/guide/for/how-to-port-forward

if you can't get that to work, what do you get from pressing windows-button+R and writing
cmd /C ipconfig && pause
and pressing enter? like this https://i.imgur.com/DVSn9Bj.png
19
Bug reports / HFS external IP not working
« Last post by TurtleMedicine on January 22, 2022, 08:10:41 AM »
when I try to open the HFS server in my browser it shows "67.160.xx.xxx took too long to respond" I cant seem to find anyone else with this issue, so its pretty annoying. when I open it as localhost it works fine.
20
after some investigation, turns out that it *does* in fact respond with a bunch of http headers, but no body, and it does keep the tcp connection alive indefinitely.. curl -v log:

$ curl 'http://127.0.0.1/123.txt' -H "Range: bytes=3-" -vv
* STATE: INIT => CONNECT handle 0x80008eff8; line 1789 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* family0 == v4, family1 == v6
*   Trying 127.0.0.1:80...
* STATE: CONNECT => CONNECTING handle 0x80008eff8; line 1850 (connection #0)
* Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)
* STATE: CONNECTING => PROTOCONNECT handle 0x80008eff8; line 1980 (connection #0)
* STATE: PROTOCONNECT => DO handle 0x80008eff8; line 2003 (connection #0)
> GET /123.txt HTTP/1.1
> Host: 127.0.0.1
> User-Agent: curl/7.80.0
> Accept: */*
> Range: bytes=3-
>
* STATE: DO => DID handle 0x80008eff8; line 2099 (connection #0)
* STATE: DID => PERFORMING handle 0x80008eff8; line 2218 (connection #0)
* Mark bundle as not supporting multiuse
* HTTP 1.1 or later with persistent connection
< HTTP/1.1 400 Bad Request
< Content-Type: text/plain
< Accept-Ranges: bytes
< Server: HFS 2.3m
< Set-Cookie: HFS_SID_=0.732762209838256; path=/; HttpOnly
< ETag: 491C3211A3BA8673626DDF909E1F59BE
< Last-Modified: Sat, 22 Jan 2022 01:00:01 GMT
< Content-Disposition: filename="123.txt";
* no chunk, no close, no size. Assume close to signal end
<

(here curl just hangs indefinitely)


wget:
$ wget 'http://127.0.0.1/123.txt' -v -c
--2022-01-22 02:25:12--  http://127.0.0.1/123.txt
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3 [text/plain]
Saving to: %u2018123.txt%u2019

123.txt                                                             100%[==================================================================================================================================================================>]       3  --.-KB/s    in 0s

2022-01-22 02:25:12 (31.1 KB/s) - %u2018123.txt%u2019 saved [3/3]


hans@DESKTOP-2LHJILI ~
$ wget 'http://127.0.0.1/123.txt' -v -c
--2022-01-22 02:25:15--  http://127.0.0.1/123.txt
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 400 Bad Request
2022-01-22 02:25:15 ERROR 400: Bad Request.


- and that 400 breaks wget's -c , which is bad when combined with -r , eg `wget -r -c http://127.0.0.1/ - will only work the first time, the 2nd invocation will be broken with a http bad request error. (because hfs doesn't respond with http 416)