DevonThink Web Server Timeout

DEVONthink Tips
1

Hi All,

While attempting to run (and use) the web server component of DevonThink, it loads and works, but the timeout (forcing a re-login) is brutally fast. I might even guess this is less than 5 minutes. This makes the web server completely unusable.

Is there a configuration file or a location somewhere I can edit the server timeout and make it something like an hour or two?

2

Which browser do you use? You shouldn’t notice this as long as the browser remembers the credentials or adds them to the keychain.

3

Hi cgrunenberg,

Thanks for the response. Sadly, it doesn’t answer the question. Hopefully the web timeout can be changed or exposed as a setting. If it can be done, please let me know how. Most major DBMS servers generally offer the ability to change these settings.

Saving the username and password in the browser does no obviate the need for timeout changes as the credential request is jarring firstly, and secondly it often resets to nothing in some scenarios. Also, in browsers like chrome, gaining access to these credentials can be easy and that’s bad from a security perspective.

Fact is, the aggressive session timeout makes the web server component highly unusable (and unacceptable) to users.

4

The next maintenance release will both revise the timeout handling and increase the timeout.

5

Sorry to bump this back to life, but I wanted to ask exactly this question.

Web server users are experiencing a timeout which is encountered in a HTTP authentication requester while the server view is still open (which means a standard requester pops up and the user is not “logged out” and redirected to the login screen).

  1. How can the login become persistent (cookie?) for at least a day/8 hours or so?
  2. Or make the login permanent with a cookie?
  3. Which settings must be specified in the browser (in our case: Firefox) so that the login isn’t “forgotten”?
6

There are no such options yet but we’ll consider this for future releases.

1 Like