I think it is advisable to change how the crawler UI authentication works, at least make it possible to deactivate it.
- The session timeout value is too short. Web applications usually have a timeout value set to 30 minutes. - The context is not remembered. If you are entering/editing a complex exclude list for a job and pressing "Save" after, say, 10 minutes, everything is lost. Many authentication models remember the last action and perform that action after reauthentication.
The latter is probably more complex to fix, but a longer session duration will probably solve the problem of lost work.
What do you others think? Erlend
