User Tools

Site Tools


transformations:webrequest

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
transformations:webrequest [2019/10/31 08:07] dmitrytransformations:webrequest [2019/10/31 11:17] – [Cookies] dmitry
Line 3: Line 3:
 Category: Workflow / External Category: Workflow / External
  
-Sends an HTTP request to a web server and receives a response. Intended for interactions with REST APIs, cloud applications and websites. Requires a configured Web Location connector.+Sends a single HTTP request to a web server and receives a response. Intended for interactions with REST APIs, cloud applications and websites. Requires a configured Web Location connector.
  
 Supports all HTTP methods - GET, POST, PUT, DELETE, HEAD, OPTIONS, CONNECT, TRACE, PATCH. Supports all HTTP methods - GET, POST, PUT, DELETE, HEAD, OPTIONS, CONNECT, TRACE, PATCH.
Line 95: Line 95:
  
 ===Fail if HTTP error, otherwise save response body into file=== ===Fail if HTTP error, otherwise save response body into file===
-In this case, if the response status is not an error (i.e. HTTP status codes 4xx or 5xx) then the response body (only body!) will be saved into the specified file verbatim.+In this case, if the response status is not an error (i.e. HTTP status codes 4xx or 5xx) then the response body (only body!) will be saved verbatim into the specified file.
  
 ====Cookies==== ====Cookies====
-Currently, there is no way to set HTTP cookies explicitly in the Web Request action. Under the hood, all cookies that come with responses are automatically stored in a cookie container that exists only during project execution. Cookies from the container are automatically appended to outgoing requests. In case of calls/iterations, the cookie container is passed to called/iterated modules or projects which in turn can add new cookies to it. This can be used for cookie-based web sessions.+Currently, there is no way to set HTTP cookies explicitly in the Web Request action. Under the hood, all cookies that come with responses to web requests are automatically stored in a cookie container that exists only during project execution. Cookies from the container are automatically appended to outgoing requests made using the same Web Location connectorIf a project workflow includes calls/iterations, the cookie container is passed to called/iterated modules or projects which in turn can add new cookies to it. This can be used for cookie-based web sessions.
  
 When project execution is finished, the cookie container is discarded. No cookies are stored in project or Web Location connector. When project execution is finished, the cookie container is discarded. No cookies are stored in project or Web Location connector.
 +
 +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.
  
 ====See also==== ====See also====
  
 * [[transformations:iteratewebrequest|Iterate Web Request]] * [[transformations:iteratewebrequest|Iterate Web Request]]
transformations/webrequest.txt · Last modified: 2023/04/21 03:52 by dmitry

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki