Namespace

glide.http

12 ServiceNow system properties in this namespace, with what each one does.

glide.http.async.client.v2.enabled This property controls whether outbound HTTP requests are routed through an asynchronous client that supports various protocols, enhancing performance.
glide.http.async.io_thread_count This property configures the number of IO threads available for asynchronous HTTP operations, impacting how efficiently requests are handled.
glide.http.cache_control It specifies the Cache-Control directive to be included in HTTP responses, influencing client-side caching behavior.
glide.http.ecc.response_poller.loop_iteration.interval_ms This property configures the interval at which the ECC Queue checks for responses, impacting the responsiveness of the system to incoming messages.
glide.http.expire.days This property specifies the number of days before static content expires in HTTP responses, allowing for control over content caching behavior.
glide.http.headers_config.enabled This property determines whether HTTP response header configurations are utilized, impacting security measures against various web vulnerabilities.
glide.http.log_debug This property allows the retrieval of all HTTP headers, including those set automatically by the system, when enabled.
glide.http.outbound.max_timeout This property defines the maximum timeout duration for asynchronous API calls, capping it at 30 seconds unless overridden by another setting.
glide.http.outbound.max_timeout.enabled This property enables or disables a hard maximum wait time for asynchronous API calls, impacting how long the system waits for a response.
glide.http.response.get_body.limit It limits the size of HTTP response bodies to mitigate risks of memory overflow and service disruption.
glide.http.response.get_body.limit.enabled This property enables a safeguard against OutOfMemoryExceptions by limiting the size of HTTP response bodies processed by the system.
glide.http.timeout This property specifies the timeout period for outbound HTTP transactions, defaulting to 175 seconds, which can be adjusted based on network performance and requirements.