User Tools

Site Tools


connectors:weblocation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
connectors:weblocation [2020/11/28 06:16] dmitryconnectors:weblocation [2023/03/09 15:54] (current) – upates for v5.4.1 craigt
Line 1: Line 1:
 ===== Web Location ===== ===== Web Location =====
  
-Specifies a web location which can later be used for sending web requests. The action supports authentication modes:+Specifies a web location that can later be used for sending web requests. The action supports authentication modes:
  
   * No authentication   * No authentication
   * Basic HTTP authentication   * Basic HTTP authentication
 +  * HTTP Digest authentication
   * Windows identity (a.k.a. Windows integrated)   * Windows identity (a.k.a. Windows integrated)
   * OAuth2   * OAuth2
 +  * API key
  
 Note that implementation of OAuth2 by some web services may require frequent renewals of refresh tokens. Since EasyMorph connectors are immutable (mutable connectors are coming in 2021) a "Web location" connector is only valid until the 1st refresh token expires, and will require re-authentication after that. Note that implementation of OAuth2 by some web services may require frequent renewals of refresh tokens. Since EasyMorph connectors are immutable (mutable connectors are coming in 2021) a "Web location" connector is only valid until the 1st refresh token expires, and will require re-authentication after that.
Line 31: Line 33:
  
 ^ Setting ^ Description ^ ^ Setting ^ Description ^
-| Request timeout  | Time in seconds after which web request will fail automatically if it's not completed by then. | +| Request timeout  | Time in seconds after which web request will fail automatically if it's not completed by then. | 
-| Use throttling | Throttling settings that limit the number of requests sent to the target web service. Specified per connector, but used on per-project basis.  |+| Use throttling | Throttling settings that limit the number of requests sent to the target web service. Specified per connector, but used on per-project basis.  |
 | Handle HTTP 429 automatically  | If the target web service responds with [[https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429|HTTP 429]] (too many requests) then EasyMorph can automatically retry sending web request after the delay specified in the server's response.  | | Handle HTTP 429 automatically  | If the target web service responds with [[https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429|HTTP 429]] (too many requests) then EasyMorph can automatically retry sending web request after the delay specified in the server's response.  |
 +| Don't send User-Agent automatically  |By default, EasyMorph sends the User-Agent HTTP header (e.g. "User-Agent: EasyMorph 5.4" - note that only the first two numbers of the current EasyMorph version are sent).  Checking this option prevents EasyMorph from including this header.|  
  
 === Tab Proxy === === Tab Proxy ===
connectors/weblocation.txt · Last modified: 2023/03/09 15:54 by craigt

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki