The problem with this version is that if you put a password on the root (the house), you can not access the folder upload, also enabling the account "can can" HFS automatically puts a password on the folder "upload" and no longer works.
As far as i can understand, you are facing this problem because of the removal of "anyone" permission in build 211.
Actually the
anonymous+any_account doesn't cover the case of someone who logged in to a user/pass protected resource. That's because that's not an account, and is not really anonymous. So, having just removed "anyone" is an error.
Let see possible solutions:
1. permission for "anonymous" could cover the case of someone logged in (with username), but with no account.
i don't like this because it's not the meaning of the word "anonymous".
2. do as in point 1, but renaming "anonymous" to something else.
maybe ok, but i don't truly like, and can't imagine a good short rename.
3. remove the "set user/pass" capability.
i think this feature is quite useless, and adds complexity to hfs (having 2 methods instead of one). we could just have a similar quick way to create an account. other than being quick, i see no other advantage of it over accounts. It's there because there was a time when hfs had no accounts.
so, i think this point will be done before or later, even if it will not be chosen as solution for the current problem.
4. re-add the "anyone" permission.
quick and safe
Opinions?