HTTP Source
Step 4 - Connection and Security Settings
Enable Basic Authentication
Works only in VM, Docker, and Kubernetes. When turned on, it authenticates each request using the Authorization header encoded in Base64 format as 'Basic encodeBase64(username:Password)'.
OFF
STRING
Client Certification Verification Type
Specifies the type of client certificate verification required. The supported values are 'Require' and 'Optional'.
SSL/TLS Protocol
Indicates the SSL/TLS protocol being used.
TLS
TLS Store Type
Specifies the type of TLS store.
JKS
STRING
SSL/TLS Configurations
Specifies configurations for SSL/TLS in the key-value pairs. Vaules can be separated by commas (',') Some supported parameters can be exemplified as
SSL/TLS protocols: ‘
sslEnabledProtocols
' as key and 'TLSv1.1,TLSv1.2
’ as values.List of ciphers: ‘
ciphers
’ as key and 'TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
' as value.Supported server names: ‘
server.supported.server.names
’ as key and 'server_name
’ as value.Add HTTP SNIMatcher: ‘
server.supported.snimatcher
' as key and 'SNIMatcher
’ as value.
STRING
Step 5 - Worker and Connection Management
HTTP Connection Idle Timeout
The time in milliseconds for which the HTTP connection can remain idle before timeout.
120000
INTEGER
Server Bootstrap Configurations
Configurations for server bootstrap in the key-value format. Some supported configurations can be exemplified as
Server Connection Timeout in milliseconds: '
server.bootstrap.connect.timeout
' as key and '15000
' as value.Server Socket Timeout in seconds: '
server.bootstrap.socket.timeout
' as key and '20
' as value.Enable TCP No Delay:
‘server.bootstrap.nodelay
' as key and 'true
' as value.Enable Server Keepalive: '
server.bootstrap.keepalive
' as key and 'true
' as value.Send Buffer Size: '
server.bootstrap.sendbuffersize
' as key and '1048576
’ as value.Receive Buffer Size: '
server.bootstrap.receivebuffersize
' as key and '1048576’ as value.Number of Connections Queued: '
server.bootstrap.socket.baklog
' as key and '150’ as value.
STRING
Step 6 - Request and Header Validations
HTTP Request Size Validation Settings
Configurations for validating the size of HTTP requests in key-value format. Some supported configurations can be exemplified as
Enable Request Size Validation: '
request.size.validation
' as the key and 'true
' as value.If request size is validated:
Maximum Request Size: '
request.size.validation.maximum.value
' as key and '2048
' as value.Response Status Code when Request Size Validation fails: '
request.size.validation.reject.status.code
' as key and '401
' as value.Response Message when Request Size Validation fails: '
request.size.validation.reject.message
' as key and 'Message is bigger than the valid size(or any message
)' as value.Response Content-Type when Request Size Validation fails: '
request.size.validation.reject.message.content.type
' as key and 'plain/text
' as value.
STRING
HTTP Header Validation Settings
Configurations for validating HTTP headers in the key-value format. Some supported configurations can be exemplified as
Enable Header Size Validation: '
header.size.validation
' as key and 'true
' as value.If header size is validated
Maximum Length of Initial Line: '
header.validation.maximum.request.line
' as key and '4096
' as value.Maximum Length of All Headers: '
header.validation.maximum.size
' as key and '8192
' as value.Maximum Length of the Content or Each Chunk: '
header.validation.maximum.chunk.size
' as key and '8192
' as value.Response Status Code when Header Validation Fails: '
header.validation.reject.status.code
' as key and '401
' as value.Response Message when Header Validation Fails: 'header.validation.reject.message' as key and '
Message header is bigger than the valid size(or any message)
' as value.Response Content-Type when Header Validation Fails: '
header.validation.reject.message.content.type
' as key and 'plain/text
' as value.
STRING
Step 7 - Preview
In Preview Step, you're provided with a concise summary of all the changes you've made to the HTTP Source Node. This step is pivotal for reviewing and ensuring that your configurations are as intended before completing node setup.
Viewing Configurations: Preview Step presents a consolidated view of your node setup.
Saving and Exiting: Use the Complete button to save your changes and exit the node and return back to Canvas.
Revisions: Use the Back button to return to any Step of modify node setup.
The Preview Step offers a user-friendly summary to manage and finalize node settings in Cortex.
Last updated