And the other thing i noticed is all though the upload is not allowed on the server I still upload the whole file before I find out that the server rejected it. Shouldnt the server just drop the connection when the upload starts instead of letting it complete?
that's how HTTP works, sorry. i already had this doubt myself.
would this be possible to fix this problem.
when i hit the upload button on the page. An upload request is sent to hfs, which then returns an allow/deny to the client. If you embed an if statement in the code on the upload page to act on the message returned from hfs to either upload the file or redirect to the error page.
it could work something like this
[b]if[/b] response [b]=[/b] allow [b]then[/b]
upload the file [b]else[/b]
redirect to error page
I dont know much about coding and http so Im just seeing if you think its worth a try.
ok, this problem is due to the not-so-old feature, that let you access any section page of the template just by typing its ~name
it's not so serious, but i guess some may be confused by the result, so i will think of it
I dont think that it is a big deal...
I just had this thought while posting
when hfs is processing the request for the template section, it could check whether or not access should be granted to it, if access is not supposed to be granted maybe hfs could send the error section instead.
