HFS: Known limits: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
* '''After login, redirect to''' works only by clicking on the ~login link --- [http://www.rejetto.com/forum/?topic=5260 see forum] | * '''After login, redirect to''' works only by clicking on the ~login link --- [http://www.rejetto.com/forum/?topic=5260 see forum] | ||
* '''Logout''' | * '''Logout''' button unavailable. The only way to logout safely is to to close your internet browser. In case of tabbed browser, closing the tab may be not enough. If after quitting the browser you appear to be still logged in, it is probably a cache problem: empty your browser's cache. | ||
=== Others === | === Others === | ||
* There is no '''Speed limit''' equivalent for the upload. This is due to the single-threaded way HFS handles connections. There's no plan about changing this because it would require a lot of work. | * There is no '''Speed limit''' equivalent for the upload. This is due to the single-threaded way HFS handles connections. There's no plan about changing this because it would require a lot of work. | ||
Revision as of 07:43, 29 November 2007
These limits are due to the fact HFS currently uses a very simple authentication system. (the one provided by HTTP itself)
It is planned in the future to switch to a better systems, based on cookies. In the while these limits will last.
- After login, redirect to works only by clicking on the ~login link --- see forum
- Logout button unavailable. The only way to logout safely is to to close your internet browser. In case of tabbed browser, closing the tab may be not enough. If after quitting the browser you appear to be still logged in, it is probably a cache problem: empty your browser's cache.
Others
- There is no Speed limit equivalent for the upload. This is due to the single-threaded way HFS handles connections. There's no plan about changing this because it would require a lot of work.