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 08:09] – [Response] 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====
transformations/webrequest.txt · Last modified: 2023/04/21 03:52 by dmitry

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki