netscaler.adc.nshttpprofile module – Configuration for HTTP profile resource.
Note
This module is part of the netscaler.adc collection (version 2.6.0).
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install netscaler.adc
.
To use it in a playbook, specify: netscaler.adc.nshttpprofile
.
New in netscaler.adc 2.0.0
Synopsis
Configuration for HTTP profile resource.
Parameters
Parameter |
Comments |
---|---|
Adapts the configured request timeout based on flow conditions. The timeout is increased or decreased internally and applied on the flow. Choices:
|
|
When enabled allows only the word characters [A-Za-z0-9_] and hyphen [-] in the request/response header names and the connection will be reset for the other characters. When disabled allows any visible (printing) characters (%21-%7E) except delimiters (double quotes and “(),/:;<=>?@[]{}”). Choices:
|
|
Choose whether to enable support for Alternative Services. Choices:
|
|
Configure a custom Alternative Services header value that should be inserted in the response to advertise a HTTP/SSL/HTTP_QUIC vserver. |
|
This option sets the satisfactory threshold (T) for client response time in milliseconds to be used for APDEX calculations. This means a transaction responding in less than this threshold is considered satisfactory. Transaction responding between T and 4*T is considered tolerable. Any transaction responding in more than 4*T time is considered frustrating. Citrix ADC maintains stats for such tolerable and frustrating transcations. And client response time related apdex counters are only updated on a vserver which receives clients traffic. |
|
Base NITRO API path. Define only in case of an ADM service proxy call Default: |
|
Name of the header that contains the real client IP address. |
|
Start data compression on receiving a TCP packet with PUSH flag set. Choices:
|
|
Reuse server connections for requests from more than one client connections. Choices:
|
|
Drop any extra ‘CR’ and ‘LF’ characters present after the header. Choices:
|
|
Drop any extra data when server sends more data than the specified content-length. Choices:
|
|
Drop invalid HTTP requests or responses. Choices:
|
|
Maximum size in bytes allowed to buffer gRPC packets till trailer is received |
|
Maximum time in milliseconds allowed to buffer gRPC packets till trailer is received. The value should be in multiples of 100 |
|
Set to Choices:
|
|
Choose whether to enable support for HTTP/2. Choices:
|
|
Choose whether to enable support for sending HTTP/2 ALTSVC frames. When enabled, the ADC sends HTTP/2 ALTSVC frames to HTTP/2 clients, instead of the Alt-Svc response header field. Not applicable to servers. Choices:
|
|
Choose whether to enable support for Direct HTTP/2. Choices:
|
|
Maximum size of the header compression table used to decode header blocks, in bytes. |
|
Initial window size for connection level flow control, in bytes. |
|
Initial window size for stream level flow control, in bytes. |
|
Maximum number of concurrent streams that is allowed per connection. |
|
Maximum number of empty frames allowed in HTTP2 connection per minute |
|
Maximum size of the frame payload that the Citrix ADC is willing to receive, in bytes. |
|
Maximum size of header list that the Citrix ADC is prepared to accept, in bytes. NOTE: The actual plain text header size that the Citrix ADC accepts is limited by maxHeaderLen. Please change maxHeaderLen parameter as well when modifying http2MaxHeaderListSize. |
|
Maximum number of ping frames allowed in HTTP2 connection per minute |
|
Maximum number of reset frames allowed in HTTP/2 connection per minute |
|
Maximum number of settings frames allowed in HTTP2 connection per minute |
|
Minimum number of HTTP2 connections established to backend server, on receiving HTTP requests from client before multiplexing the streams into the available HTTP/2 connections. |
|
Choose whether to enable strict HTTP/2 cipher selection Choices:
|
|
Choose whether to enable support for HTTP/3. Choices:
|
|
Maximum number of HTTP/3 streams that can be blocked while HTTP/3 headers are being decoded. |
|
Maximum size of the HTTP/3 header field section, in bytes. |
|
Maximum size of the HTTP/3 QPACK dynamic header table, in bytes. |
|
Application pipeline request buffering size, in bytes. |
|
Maximum time to wait, in milliseconds, between incomplete header packets. If the header packets take longer to arrive at Citrix ADC, the connection is silently dropped. |
|
The ID of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The IP of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The name of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The password of the managed NetScaler instance. Define only in case of an ADM service proxy call In Settings > Administration > System Configurations > Basic Settings, if you select Prompt Credentials for Instance Login, ensure to configure username and password of a managed instance. |
|
The username of the managed NetScaler instance. Define only in case of an ADM service proxy call In Settings > Administration > System Configurations > Basic Settings, if you select Prompt Credentials for Instance Login, ensure to configure username and password of a managed instance. |
|
Mark CONNECT requests as invalid. Choices:
|
|
Mark HTTP/0.9 requests as invalid. Choices:
|
|
Mark Http header with extra white space as invalid Choices:
|
|
Mark RFC7230 non-compliant transaction as invalid Choices:
|
|
Mark TRACE requests as invalid. Choices:
|
|
Number of bytes allowed for header field for HTTP header. If number of bytes exceeds beyond configured value, then request will be marked invalid |
|
Number of bytes to be queued to look for complete header before returning error. If complete header is not obtained after queuing these many bytes, request will be marked as invalid and no L7 processing will be done for that TCP connection. |
|
Maximum number of requests allowed on a single connection. Zero implies no limit on the number of requests. |
|
Maximum limit on the number of connections, from the Citrix ADC to a particular server that are kept in the reuse pool. This setting is helpful for optimal memory utilization and for reducing the idle connections to the server just after the peak time. Zero implies no limit on reuse pool size. If non-zero value is given, it has to be greater than or equal to the number of running Packet Engines. |
|
Minimum limit on the number of connections, from the Citrix ADC to a particular server that are kept in the reuse pool. This setting is helpful for optimal memory utilization and for reducing the idle connections to the server just after the peak time. Zero implies no limit on reuse pool size. |
|
Name for an HTTP profile. Must begin with a letter, number, or the underscore \(_\) character. Other characters allowed, after the first character, are the hyphen \(-\), period \(.\), hash \(\#\), space \( \), at \(@\), colon \(:\), and equal \(=\) characters. The name of a HTTP profile cannot be changed after it is created. CLI Users: If the name includes one or more spaces, enclose the name in double or single quotation marks \(for example, “my http profile” or ‘my http profile’\). |
|
The IP address of the NetScaler ADC appliance acting as a proxy server. Define only in case of an ADM service proxy call Choices:
|
|
The authentication token provided by a login operation. |
|
The password with which to authenticate to the NetScaler ADC node. |
|
Which protocol to use when accessing the nitro API objects. Choices:
|
|
The username with which to authenticate to the NetScaler ADC node. |
|
The ip address of the NetScaler ADC appliance where the nitro API calls will be made. The port can be specified with the colon (:). E.g. 192.168.1.1:555. |
|
Pass protocol upgrade request to the server. Choices:
|
|
Generate the persistent Citrix ADC specific ETag for the HTTP response with ETag header. Choices:
|
|
Time, in seconds, within which the HTTP request must complete. If the request does not complete within this time, the specified request timeout action is executed. Zero disables the timeout. |
|
Action to take when the HTTP request does not complete within the specified request timeout duration. You can configure the following actions: * RESET - Send RST (reset) to client when timeout occurs. * DROP - Drop silently when timeout occurs. * Custom responder action - Name of the responder action to trigger when timeout occurs, used to send custom message. |
|
Idle timeout (in seconds) for server connections in re-use pool. Connections in the re-use pool are flushed, if they remain idle for the configured timeout. |
|
Allow RTSP tunnel in HTTP. Once application/x-rtsp-tunnelled is seen in Accept or Content-Type header, Citrix ADC does not process Layer 7 traffic on this connection. Choices:
|
|
If The module will not save the configuration on the NetScaler ADC node if it made no changes. Choices:
|
|
The state of the resource being configured by the module on the NetScaler ADC node. When When When Choices:
|
|
If Choices:
|
|
Enable or disable web logging. Choices:
|
|
HTTP connection to be upgraded to a web socket connection. Once upgraded, Citrix ADC does not process Layer 7 traffic on this connection. Choices:
|
Notes
Note
For more information on using Ansible to manage NetScaler ADC Network devices see https://www.ansible.com/integrations/networks/citrixadc.
Examples
---
- name: Sample Playbook
hosts: localhost
gather_facts: false
tasks:
- name: Sample Task | nshttpProfile
delegate_to: localhost
netscaler.adc.nshttpprofile:
state: present
name: httpprofile-HTTP2-0
http2: ENABLED
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Indicates if any change is made by the module Returned: always Sample: |
|
Dictionary of before and after changes Returned: always Sample: |
|
List of differences between the actual configured object and the configuration specified in the module Returned: when changed Sample: |
|
Indicates if the module failed or not Returned: always Sample: |
|
list of logged messages by the module Returned: always Sample: |