Stores the setup information used by the SRP HTTP Framework. The layout looks like this:
| Attribute | Name | Description |
|---|---|---|
<1> | Home URL | Identifies the primary URL of the website, e.g., www.mywebsite.com. |
<2> | API URL | Identifies the path that is appended to the Home URL wherein the entry point of the API begins, e.g., /api The HTTP_Service_Setup uses the above information to create proper RESTful responses wherein paths to other web service APIs need to be included within the response. Thus, in the above examples, the two are joined when creating fully resolved API URLs, e.g., www.mywebsite.com/api/<service> |
<3> | Capture Path | Used in HTTP_MCP to identify the local OS path where request and response content can be saved for off-line analysis. If the path does not exist, then no attempt to store this information will be made. |
<4> | Enable Authentication Flag | Boolean setting that determines if authentication is enabled. Used by HTTP_Authentication_Services. Note: Only an explicit value of 0 (False) will disable authentication. Any other value, including an empty value, will enable authentication. |
<5> | Realm Value | Used with HTTP authentication to associate resource links to the same protective space. |
<6> | Entry Point Service | Name of the entry point web service. This is used by HTTP_MCP to call the first web service. This should not include the standard HTTP prefix or SERVICES suffix. The default value is entry_point. |
<7> | Flush Cache Flag | Boolean setting that determines if code should be flushed when the web service is finished. This allows changes in web service procedures to always be available without having to restart the OEngineServer. |
<8> | Non-Authenticated URLs | @VM list of URLs that should not be authenticated. This includes URLs that support OAuth redirects since these requests will unlikely be authenticated (although they should be secret and secure with the OAuth authenticating server). |
<9> | Aborted Service | Service handler for HTTP Requests that get aborted either due to Runtime Errors or Status Errors. If the Debugger Intercept has been enabled, this handler will only receive Status Error aborts. |
<10> | Enable Logging Flag | Boolean setting that determines if logging is enabled. This is used by the CreateLogFile service. Note: Only an explicit value of 0 (False) will disable logging. Any other value, including an empty value, will enable logging. |
<11> | Debugger Setting | Debugger Setting value that will be passed into the RTI_Debugger_Setting subroutine. 0=Disabled, 1=Enabled, and 2=Intercept. If value is 2, the value of HTTP_FRAMEWORK_SETUP_DEBUGGER_INTERCEPT$ will be used to determine the name of the intercept stored procedure. |
<12> | Debugger Intercept | Service handler for HTTP Requests that abort due to a Runtime Error and the Debugger Intercept has been enabled. See HTTP_FRAMEWORK_SETUP_DEBUGGER_SETTING$. |
<13> | Log Errors Only | Boolean setting that determines if only error responses (i.e., status codes of 4xx or 5xx) should be logged. This is used by the CreateLogFile service. Note: Only an explicit value of 0 (False) will disable logging. Any other value, including an empty value, will enable logging. |
