HTTP Server

Settings: HTTP Server
Settings: HTTP Server
  • Caption: ‘Caption’ is the title shown in the title bar. It also allows you to identify the server in your task manager if you have more than one Berkeley Web Server running.

  • Start: Delay in seconds before server starts listening for requests.

  • Proxy redirect: When using a proxy server you can define a proxy string here. Configure the proxy server accordingly to route requests.

  • Server port http: Server port is the port on which the Berkeley Webserver listens for requests.

  • Server port https: Server port is the secure port on which the Berkeley Webserver listens for requests, you need to set the right certificates on the tab Security.

  • Parameter newname: When opening a case, one can give it a new name in the request parameters. Here is where you can define the name of that parameter. In other words, if you define parameter newname to be ‘foo’, foo=number5, the case will have the name ‘number5′. Defaults to ‘newname’.

  • Close instance after: ‘Close instance after’ defines how long to keep cases in memory in case of inactivity in minutes. The effect of this setting is not noticeable to the end user (but don’t set it to 0), other than that something may have to be loaded from disk when the user starts navigating again. When an instance is closed because the minutes defined here have lapsed (opposed to a forced closing) it will be written to disk as cache. When the user then continues with the instance, and still has a valid session, the cache file will be loaded in memory again, and its state restored.

  • Close session after: ‘Close session after’ defines how long sessions will be valid in hours. As long as the session is still valid the connection between the browser and the webserver remains intact. When the session is closed, a new browser window has to be started to continue using the case. These settings may be used to optimize the server capacity according to actual usage.

  • Automatic server start: If checked, the Web Server will start listening for requests automatically when the application is started, after a delay of Start seconds.

  • Save on exit: ‘Save on exit’ makes sure cases will be saved to disk and available to be opened in a later session.

  • Save on step: ‘Save on exit’ makes sure cases will be saved to disk and available to be opened in a later session.

  • Allow webadmin: When checked the settings can also be maintained through a web interface.

  • Allow save by user: Allow a user to save the current session locally. Note that to be able to make use of this feature some things have to be added to the web environment.