transformations:webrequest
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
transformations:webrequest [2019/10/31 08:09] – [Response] dmitry | transformations:webrequest [2019/10/31 11:17] – [Cookies] dmitry | ||
---|---|---|---|
Line 98: | Line 98: | ||
====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. | + | Currently, there is no way to set HTTP cookies explicitly in the Web Request action. Under the hood, all cookies that come with responses |
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: | * [[transformations: |
transformations/webrequest.txt · Last modified: 2023/04/21 03:52 by dmitry