It should contain a comma separated list of hosts to opt out of proxying. These variables provide a granular way to opt out of proxying, on a per-host basis. Request is also aware of the NO_PROXY/ no_proxy environment variables. Furthermore, the proxy configuration option can be explicitly set to false / null to opt out of proxying altogether for that request. It is valid to define a proxy in one of the environment variables, but then override it for a specific request, using the proxy configuration option. Similarly, HTTPS_PROXY / https_proxy will be respected for SSL requests that do not have an explicit proxy configuration option. When HTTP_PROXY / http_proxy are set, they will be used to proxy non-SSL requests that do not have an explicit proxy configuration option present. The following environment variables are respected by request: Controlling proxy behaviour using environment variables Never sent to the endpoint server, but only to the proxy server. Header and any headers from custom proxyHeaderExclusiveList are Note that, when using a tunneling proxy, the proxy-authorization Headers only with the proxy and not with destination host. You can also set the proxyHeaderExclusiveList to share certain ProxyHeaderWhiteList to share certain headers with the proxy. If you are using a tunneling proxy, you may set the Tunnel : false, but note that this will allow the proxy to see the traffic You can also make a standard proxied http request by explicitly setting
To force a tunneling proxy, you may set the tunnel option to true.
Or other features, it is generally simpler to go with a Section of the initial line of the request a fully qualified url toįor example, it will make a single request that looks like: HTTP/1.1 GET īecause a pure "http over http" tunnel offers no additional security On port 80, and return a response that looks like: HTTP/1.1 200 OKĪt this point, the connection is left open, and the client isĬommunicating directly with the machine.īy default, when proxying http traffic, request will simply make a User-Agent: whatever user agent you specifyĪnd then the proxy server make a TCP connection to endpoint-server That is, first it will make a request like: HTTP/1.1 CONNECT :80 Then use the supplied connection to connect to the endpoint. Request will send a CONNECT request to the proxy server first, and If your endpoint is an https url, and you are using a proxy, then Redirects) will be sent via a connection to the proxy server. If you specify a proxy option, then the request (and any subsequent Automatically generate the body hash by passing body_hash: true.Manually generate the body hash and pass it as a string body_hash: '.'.Pass transport_method : 'query' or transport_method : 'body' in the OAuth.To send OAuth parameters via query params or in a post body as described in The Instead of consumer_secret, specify a private_key string in.The following changes to the OAuth options object: Request supports application/x-application/x-www-form-urlencoded (URL-Encoded Forms) request-promise-any (uses any-promise Promises)Īlso, util.promisify, which is available from Node.js v8.0 can be used to convert a regular function that takes a callback to return a promise instead.request-promise-native (uses native Promises).request-promise (uses Bluebird Promises).Several alternative interfaces are provided by the request team, including: These wrappers can be useful if you prefer to work with Promises, or if you'd like to use async/ await in ES2017. If you'd like request to return a Promise instead, you can use an alternative interface wrapper for request. Request supports both streaming and callback interfaces natively. You can still use intermediate proxies, the requests will still follow HTTP forwards, etc.
0 kommentar(er)
