rejetto forum
Software => HFS ~ HTTP File Server => Topic started by: Anonymous on October 27, 2003, 02:46:10 AM
-
Thanks for hard work, rejetto!
You fixed the MIME and the headers bug!
You have also added an option to not send the HFS identifier :D
Thank You very very much! :)
Now just for a few questions:
1. The Realm for the password protected page isn't customizable, right?
For ex. "Password protected resource" That is not customizable via the template? Am I right about that?
2. And how about the 401 page? is it customizable via the template?
"401 - You are not authorized to access this file"
Thanks a ton for your hard work, rejetto!! :)
-
1. and 2.
yes, it is not customizable
does someone desire to?
-
To my experience, HFS uses the comments for a password protected source if it exists. But it would be nice to customize it without a comment and also be able to change the default realm. "Password Protected Resource"
And because of the realm, it might be nice to also be able to customize HTTP 401 pages. (Customize HTTP 401 pages for different protected source; such as different HTTP 401 pages for each folder)
One more thing about the HTTP headers: Is it right that HFS is capping all letters in its responses?
Ex:
HTTP/1.1 404 NOT FOUND
instead of
HTTP/1.1 404 Not Found
Just a little thing I notice there... :D (I know it won't make a difference, but most servers are doing Title Case, except for HTTP/1.1 200 OK)
-
I would also like to see 1 & 2 customisable if possible! ;)
keep up the great work! hfs is my favourite soft!
-
ok
-
Here is a small problem ("list index out of bounds"):
(http://rafi_d.50free.net/temp/hfs_problem.jpg)
And how to try reporoduce it (win98SE _ IE6):
- run HFS and try use the same file structure with passwords
- browse the home root (and login)
- right click on the first GIF files and do "open in a new window"
the gif tries to open, but does not succeed.
-
Found bug in 1.5d:
1. Add a folder by dragging it into HFS.
2. Click Yes when asked to be auto-updated.
3. Move your mouse over the added folder...
HFS crashes...
-
I tried what Rafi said in the prev post, and it seems that it works fine under XP, but then I find this bug:
"HFS does not encode ASCII chars. in browser"
For example, if you were to share "1+1.gif" and access it by going to the main page first, you would get an HTTP 404 Error.
But if you copied the link from HFS (the program itself), which encodes the + char into: "%2B1", the link would work fine.
But the browser does not encode the + into %2B1 and therefore gives a 404 error.
-
Found bug in 1.5d:
1. Add a folder by dragging it into HFS.
2. Click Yes when asked to be auto-updated.
3. Move your mouse over the added folder...
HFS crashes...
:( it seems it is caused by the UPX compression.
that is, it is an UPX bug, not HFS.
it does not happen, in facts, if the exe file is not compressed.
I tested UPX with several options, tried the last beta version, also tried to modify my code. But the bug remains.
However i noticed that if i remove the dialog box of step#2, the bug disappears. I could try to replace it with another dialog, maybe.
For now, i just replaced the archive on the website with an archive which contains a non-compressed exe file. But i would like to find a workaround.
-
How about not using any packers at all?
That would solve the problem :)
Thanks for your hard work, rejetto!
-
i changed the dialogs code and now it works
i will take a look at other bugs before uploading the new version
-
rafi, i'm unable to reproduce your bug
maybe if you send me in email the VFS, it could help
about the "+" bug... i can't reproduce it, it works perfectly here.
i tried both with folder and files, with IE and Opera, and what i get is always
<tr><td class=row><a href="/1%2B1"><img align=top src="/~img_folder"> <b>1+1</b></a><td colspan=3 align=center class=row><i>folder</i>
-
I will.
BTW - it happens always ONLY the first time you do it after running the HFS SW.
[/i]
-
i just published 1.5e
-
+ Bug, here's what I did to reproduce it:
1. Open HFS and share a file called 1+1.gif
2. Goto root of HFS using your browser (IE6): /
3. Click on 1+1.gif as shown on the browser (IE6).
4. HTTP 404 Not Found occurs.
P.S. Besides the character +, the character # will also causes this problem. (IE6)
In order to download the file, HFS will need to encode the hyperlink in the root page into:
http://127.0.0.1/1%2B1.gif
instead of:
http://127.0.0.1/1+1.gif
P.S. 127.0.0.1 is for this example only!
-
Sorry about the last post, but it seems that my browser encoded 1%2B1.gif into 1+1.gif.
So the 1st link would be: (HFS should encode URL in web pages into:)
root/1%2B1.gif
instead of:
root/1+1.gif
Hope it works this time :D
-
Hmmm...
I get the problem now... it seems that my web filter is making this bug:
But is it better to have HFS encode 1+1.gif into 1%2B1.gif?
Thanks rejetto! :)
-
this could lead to potential incompatibility with other (standard compliant) softwares
i do not want to risk to be incompatible with standard software to support a bug of a specific program ;)
if this buggy software is recognizable through http headers we could make a specific support