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. |
