0.2.8 ✔️

Summary

This release focuses on improvements to the HTTP client node. New features include support for easily making requests with form data, and sending plain-text request bodies with arbitrary content types. Server constraints for cache items and KV store value sizes has increased to 20K items with a 5 KiB value limit.

Breaking changes

None.

Fixes

• 🐞fix that the http client node could incorrectly produce a response body > 256 KiB limit error for HTTP responses with a zero Content-Length and a 204 status code

Features

HTTP client node

• ⚡💠 http client node: support additional request methods HEAD, OPTIONS and TRACE

• ⚡💠 http client node: support form data parameters in node configuration.

Detail

When form data configuration is present on the HTTP client node;

• The Content-Type request header is automatically set to application/x-www-form-urlencoded
• If a Content-Type request header is configured with a value multipart/form-data, then multipart requests are made
• Other values for the Content-Type header are ignored and overwritten (except multipart/form-data)
• Request bodies cannot be simultaneously configured with node input or a configured JSON body

 

• ⚡💠 http client node: when “Emit response body” option is enabled, node output now contains a body_bytes property. It’s value is the number of bytes read from the HTTP response body.

Detail

If the HTTP server is well-behaved, the value of body_bytes should match the Content-Length header, if the latter is present.

Having the byte size of the body available is useful in post-processing. For example, it can be used to modify the output or cause a node error if the response body size is unexpectedly small or large.

 

• ⚡💠 http client node: support sending plain-text request bodies

Detail

The HTTP client node will allow plain text request bodies when:

1. The “Send input data” is enabled
2. The node input data is a JSON string value (json:string in the flow editor)
3. A Content-Type header is configured, with a value other than application/json

Enhancements

• 🔼💠 http client node: when a request body contains JSON data, the default Content-Type header is now application/json; charset=utf-8. Formerly, application/json was used.

• 🔼💠 http client node: when a Content-Type header is present in node configuration, the node will not override it, unless form data is used

• 🔼💠 http client node: the safety feature that limits response bodies to 256 KiB of data has been re-implemented in a more robust manner.

Detail

Reading response bodies are avoided when a response contains a Content-Length header which exceeds the read limit.

Irrespective of the Content-Length header, which may be maliciously manipulated, attempts to read response bodies will fail and stop once the read limit is reached, without allocating additional memory.

This prevents memory exhaustion and other execution issues when:

• HTTP response bodies become too large for Sirveo to process safely and reliably
• accidentally making a request to an endpoint that responds with 100 MiB of data
• a misbehaving (or malicious) HTTP server responds with a massive response body

Internal

• ⚙️ server: increase KV store cache size from 10K to 20K, and max value size from 2048 to 5120 bytes

• ⚙️ downgrade a dependency related to schedule triggers, which could not be verified for stability