Activity
From 03/31/2021 to 04/29/2021
04/23/2021
- 04:04 AM Feature #5279: add support for an optional maintenance program that executes before any other ses...
- The idea is that an optional "maintenance program" can be configured to execute when the FWD server starts such that ...
- 04:01 AM Feature #5279 (New): add support for an optional maintenance program that executes before any oth...
04/22/2021
- 10:10 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- OK. I will close this task when the documentation for #4405-14 is complete.
04/19/2021
- 11:49 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- Please look at this part of @WebServer.getWebContentHandlers@...
- 11:27 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- Greg Shah wrote:
> As part of the changes for #4204, Sergey implemented "public" static HTML resources. The changes...
04/17/2021
- 10:07 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- I've put together a simple page to describe the feature "Static Web Content":/projects/p2j/wiki/Static_Web_Content. ...
- 08:58 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- Please document how to configure the @web-static-content@ section of the directory in the "Web Server":/projects/p2j/...
- 08:43 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- As part of the changes for #4204, Sergey implemented "public" static HTML resources. The changes can be seen in 3821...
- 09:48 AM Feature #5262: add access control for resources exposed via web services/protocols using the Secu...
- Support for static web content was added in #4405. This support is just for @GET@ and is currently unsecured (all re...
- 09:31 AM Feature #5262 (New): add access control for resources exposed via web services/protocols using th...
04/13/2021
- 08:48 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- OK, but make sure it is separated from FileSystemOps. That code calls down to the FWD client and uses a legacy 4GL s...
- 08:20 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- I am going to use the existing functionality of @FileSystemOps@...
- 08:16 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- > Thus the directory settings can be looked like
Yes, this is good. How are you going to handle the jar resource ... - 08:15 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- > The nodes under @web-static-content@ hold the mapping of static application contexts to their storage locations wit...
- 07:58 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- > Is this understanding correct that these static resources are managed by the existing FWD web server
Use the exi... - 05:33 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- I forgot to add welcome files. Thus the directory settings can be looked like...
- 03:46 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- Planning to add these settings to the directory under the default server node...
- 02:56 AM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- Is this understanding correct that these static resources are managed by the existing FWD web server that manages web...
04/12/2021
- 04:42 PM Feature #4405: provide the capability to deliver static HTML and resources via the FWD server's J...
- I think the initial approach would just allow access to FWD server resources without the security limits. It would a...
04/01/2021
- 06:58 AM Support #5221: Initialization failure during server runtime
- For the appservers agents to start, the FWD server must have SSL enabled.
By changing the server account name (whi... - 02:54 AM Support #5221: Initialization failure during server runtime
- I changed server-id on server.xml because I got error mentioned above "server ID <standard> has no account".
Maybe... - 02:35 AM Support #5221: Initialization failure during server runtime
- You've mentioned that you had to change the server-id on server.xml.
Why did you need to do this? The 'standard' ... - 02:30 AM Support #5221: Initialization failure during server runtime
- I have three aliases "shared", "appserveris_alias", "rest_server".
03/31/2021
- 01:28 PM Support #5221: Initialization failure during server runtime
- Is the error when trying to start an appserver?
If so, it may be because the alias for the appserver certificate, ... - 09:21 AM Support #5221: Initialization failure during server runtime
- I cant understand, what kind of certificates should be "trusted" getting this error:...
- 06:24 AM Support #5221: Initialization failure during server runtime
- I found the solution. It was not changed server-id on server.xml file.
Also available in: Atom