rejetto forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - rejetto

Pages: 1 2 3 ... 889
the only difference left is the cookie hfs tries to set, but HFS works even if the browser refuses the cookie

Code: [Select]
c:\util>curl -I
HTTP/1.1 200 OK
Content-Type: video/mp4
Content-Length: 524161548
Accept-Ranges: bytes
Server: HFS 2.4.0 RC7
Set-Cookie: HFS_SID_=e0SaJbzE5UAAAIBHD4buPw; path=/; HttpOnly
ETag: 0cd4cf64c6d11ec7c056552509854b36
Last-Modified: Wed, 07 Nov 2018 23:47:05 GMT

c:\util>curl -I
HTTP/1.1 200 OK
Date: Thu, 20 Jan 2022 19:07:02 GMT
Content-Type: video/mp4
Content-Length: 524161548
Connection: keep-alive
Keep-Alive: timeout=60
Server: Apache
Last-Modified: Wed, 07 Nov 2018 23:47:05 GMT
ETag: "1f3e120c-57a1bbc53825f"
Accept-Ranges: bytes

hfs 3 is a work-in-progress. I'm already using it.
you can contact me privately if you want me to help you setting it up.

i curl'ed it and i see the "disposition" is gone, temporarily as you say.
it plays nicely on my android, but i guess this won't cheer you up a bit.
do you want to give hfs 3 a try? i may assist you in configuration since it's still harder to use than hfs2, but i need beta testers

Menu  > debug > no content-disposition

you are right, the script is not working as expected.

i even tried this, but it didn't work
{.add header|Content-Disposition: inline.}

very disappointing.


anyway, you may parallelize multiple requests but not multiple segment of a single request, because they may depend on the state changed by another

HFS ~ HTTP File Server / Re: a new beginning...
« on: Today at 01:38:45 PM »
ignore those warnings, because they involve libs used only by the dev environment.
if you "npm audit --production"
you'll get "found 0 vulnerabilities"

i'm including this in the instructions

ok, now you got Content-Disposition: filename="The_Walking_Dead_S09E01.mp4";
before you had Content-Disposition: attachment; filename="The_Walking_Dead_S09E01.mp4";
you can see the difference.
if this is not yet enough, it's the whole line that must be wiped, and HFS allows you to do it, is just a bit trickier.
From some investigation I suspect that hfs SHOULD do that by protocol automatically, and if so it should be considered a bug.
Anyway, you can workaround this opening Events (in the menu or ALT+F6), and add something like this

{.if not|{.pos|attach|{.header|Content-Disposition.}.}|{:
  {.remove header|Content-Disposition.}

if you use curl -I <url> you'll see the differences between one request and the other.
The only difference I see is in "Content-Disposition"
that you can change by using the "Open directly in browser" option. I think it's under "other options"

HFS ~ HTTP File Server / Re: Hosting and PDF viewing
« on: Yesterday at 04:47:54 PM »
ok you can disable the attachment thing:
Menu > other options > open directly in browser

the port problem with HFS 3 is that it's not clear that the # at the beginning is to disable the line, so your changes are actually ignored.
Remove it.
I will consider this thing for next release.

HFS ~ HTTP File Server / Re: a new beginning...
« on: Yesterday at 11:28:04 AM »
in the paste i've met issues using transparency for fonts, for the sake of shading, and in this case it's easy to decided a opaque code for the final color.
#8ac may do the job

HFS ~ HTTP File Server / Re: Hosting and PDF viewing
« on: Yesterday at 08:13:49 AM »
it doesn't like something in the hfs answer but it's hard to know what.
if you would know, it could be possible that you can modify hfs answer to comply.
you can try to file this as a big to adobe.
you may also make a test with hfs 3, but beware it's a very different program and you will start from zero

HFS ~ HTTP File Server / Re: a new beginning...
« on: January 18, 2022, 05:49:04 PM »
...and HFS 3 just got https support :)
i hope we'll be able to integrate letsencrypt automatic generation, maybe as a plugin

hi, i keep my root unprotected, so i consider it safe.
Those are attempts at exploiting old bugs not present in current version.
Still those messages are annoying to look at. It would be nice if someone comes with filter to avoid those requests from being received/displayed, even just for peace of mind.

Bugs can be nasty, every software has some from time to time. Point is: adding authentication is not necessarily a solution, it just depend if the bug is accessible without of it interfering.
In real world you should just keep your software updated and check there is no known security problem with latest version.
This is true for any software out there.

btw, i'm working on HFS 3 these days. I hope it will officially replace "current" version in 1-3 months. I already use it with great satisfaction.

HFS ~ HTTP File Server / Re: a new beginning...
« on: January 18, 2022, 12:16:47 PM »
ciao mandoz, don't worry, i was just surprised someone would want/need to use IE on win10
and then i declared it won't work.
i'm using portable chrome for testing purposes (compatibliity), so it's not a matter of being portable.

:) good luck

your gitlab link says Page Not Found

Pages: 1 2 3 ... 889