...
- Connection timeouts and other connection-related configuration.
- Proxy information
- Security and certificate information.
- In-memory or file backed caching. This caching is at the HTTP client level and allows a reduction of the HTTP traffic since data is only loaded when it has gone out of date. However, these caches do not survive the lifetime of the HttpClient, and so are not available across IdP restarts, so they are generally not of a lot of value.
For details on some advanced usage, refer to the HttpClientConfiguration topic.
Notably, this feature does not at present support the security features that are described in that topic. This may be corrected in a future version. For the time being this feature only supports unauthenticated access to resources.
Configuring the HTTP Resource
...
FileBackedHTTPResource provides file backup for when the web server is unavailable, including across restarts. Note that this use case is orthogonal to the use of a file-backed HttpClient cache, which provides a local copy of valid cached data even when the web server can be contacted.
Simple Examples
...
The first example is the simplest case, with a standard client and some timeout settings.
...