Rejetto,
Thanks for doing such a good job on HFS. I have been testing HFS and all of it's alpha and beta versions for about a year now and the program is evolving very good.
I have a few comments with regards to the last v2.0 beta 15 that maybe you can look into:
1. Root Folder Comment:
It works as it is expected to work but there is one problem with it and it has to do with login.
- if the root "/" restrict access is set to "NONE" and a person attempts to log in they are presented with the normal browser login popup asking for username and password etc. Also, this popup shows a message that says "Password Protected Resource" which is what it should be.
- **BUT** if the root "/" restrict access is set to "ALL" (which is the way I Normally have it set) the browser popup asking for username and password shows a message that doesn't say "Password Protected Resource" but says whatever folder comment that has been used for the root folder including any html coding? This is wrong and has to be fixed.
2. Limits:
Having limits is definitely needed with a http server as you are working with a limited amount of bandwidth.
Your latest two additions for max contempory downloads was definitely needed and work the way they are expected to work by limiting the amount of downloads a person can download at the same time. However, I have a few comments I would like to make and maybe you can look into this:
- when max downloads has been reached or if max connections etc. have been reached up pops the 503 Server is overloaded, retry later page. That must be an internal HFS message because it isn't coming from the [overload] section in the template. As a matter of fact when do the [overload], [unathorized], [deny], and [ban] sections from the template get used? The messages I have ever seen appear to be internal from HFS itself because they are different than what is in the template.
- the 503 Server is overloaded, retry later message I don't like. That message to me, and others that have received it, infers that the server is to slow and can't keep up with the traffic which isn't true at all and is deceiving to anyone that receives it. The message should be more meaningful with a "true" message of why it is being displayed. If for example the max download limit has been reached, it should say something like "The maximum number of downloads at one time limit setup by admin has been reached, retry later" but not that the server is overloaded.
- This is the worst part about all of the limit settings except for disabled.... If there is a limit setting of any kind in limits it affects the whole server in a negative way. For example, images that don't load especially when you have many users on your server at the same time. They could be file or folder icons, button icons, a logo, page of wallpaper thumbnails etc. don't all load if **any** of the limits are enabled. If the limit, whether it be a connection limit or a download limit, is reached the images stop loading. Even browser refreshing doesn't always load all images which sure doesn't look good on your page.
- I think the HFS concept of limits has to be re-thought and looked at again.
Thank you and hope you can answer my concerns because they affect everybody using HFS.