![]() ![]() Outside of a custom data connector context, only a subset of response headers is available (for security reasons). The headers of the HTTP response are available as metadata on the binary result. POST requests may only be made anonymously. The HTTP request is made as either a GET (when no Content is specified) or a POST (when there is Content). Content: Specifying this value changes the web request from a GET to a POST, using the value of the option as the content of the POST.RelativePath: Specifying this value as text appends it to the base URL before making the request.ManualStatusHandling: Specifying this value as a list will prevent any builtin handling for HTTP requests whose response has one of these status codes.IsRetry: Specifying this logical value as true will ignore any existing response in the cache when fetching data.ExcludedFromCacheKey: Specifying this value as a list will exclude these HTTP header keys from being part of the calculation for caching data.Timeout: Specifying this value as a duration will change the timeout for an HTTP request.Headers: Specifying this value as a record will supply additional headers to an HTTP request.The actual key value is provided in the credential. ApiKeyName: If the target site has a notion of an API key, this parameter can be used to specify the name (not the value) of the key parameter that must be used in the URL.Query: Programmatically add query parameters to the URL without having to worry about escaping.The record can contain the following fields: An optional record parameter, options, may be provided to specify additional properties. Returns the contents downloaded from url as binary. Web.Contents( url as text, optional options as nullable record) as binary ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |