transformations:webrequest
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
transformations:webrequest [2021/07/02 21:42] – [Action settings] craigt | transformations:webrequest [2023/04/21 03:52] (current) – [Request Body settings] dmitry | ||
---|---|---|---|
Line 81: | Line 81: | ||
\\ | \\ | ||
__**Form**__\\ | __**Form**__\\ | ||
- | This body type is equivalent to submitting a web-form. Name-value pairs are encoded as if it was a web-form. | + | This body type is equivalent to submitting a web form. Name-value pairs are encoded as if it was a web-form. |
Header Content-Type is automatically set to " | Header Content-Type is automatically set to " | ||
Line 99: | Line 99: | ||
\\ | \\ | ||
__**File**__\\ | __**File**__\\ | ||
- | The request body is read from the specified file and inserted verbatim. | + | The request body is read from the specified file and inserted verbatim. When //Upload file (multi-part upload)// is selected, additional parameters can be defined as well. |
\\ | \\ | ||
Line 131: | Line 131: | ||
When developing workflows with web requests it may be necessary to re-run parts of workflows. In this case, it is recommended to always start from the Web Request actions that do authentication so that the session cookies can be set under the hood. | When developing workflows with web requests it may be necessary to re-run parts of workflows. In this case, it is recommended to always start from the Web Request actions that do authentication so that the session cookies can be set under the hood. | ||
+ | Web Request automatically sends the // | ||
+ | |||
+ | \\ | ||
+ | =====Community examples===== | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
\\ | \\ |
transformations/webrequest.txt · Last modified: 2023/04/21 03:52 by dmitry