Skip to content

Added docs for content-length header's behaviour in Call Rest Action #10905

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adeel2023 wants to merge 1 commit into
base: development
Choose a base branch
from
Open

Added docs for content-length header's behaviour in Call Rest Action #10905

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .../microflows-and-nanoflows/activities/integration-activities/call-rest-action.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,10 @@ The **Password** property defines the password that will be used to authenticate

These headers are added to the HTTP request header. Each custom header is a pair with a key and a value (a microflow expression).

{{% alert color="info" %}}
The actual computed-value for **Content-Length header** takes precedence over the user-specified value. Incase of unkown length (e.g. streamed or binary content), user-specified value is used.
{{% /alert %}}

{{% alert color="warning" %}}
REST endpoints which are using NGINX as a webserver will ['silently drop'](https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#missing-disappearing-http-headers) HTTP headers which contain an underscore `_`.
{{% /alert %}}
Expand Down