Request

URL is the parsed and validated URL of the request.

Outgoing requests are always sent to the preconfigured backend provided to the send method. The URL is used for the request resource, Host header, etc.

Proto contains the HTTP protocol version used for incoming requests.

These fields are ignored for outgoing requests.

Body is the request's body.

For the incoming client request, the body will always be non-nil, but reads may return immediately with EOF. For outgoing requests, the body is optional. A body may only be read once.

Prefer using the SetBody method over assigning to this value directly, as it enables optimizations when sending outgoing requests. See the SetBody documentation for more information.

RemoteAddr contains the IP address of the requesting client.

This field is ignored for outgoing requests.

ServerAddr contains the IP address of the server that received the HTTP request.

This field is ignored for outgoing requests.

SendPollInterval determines how often the Send method will check for completed requests. While polling, the Go runtime is suspended, and all user code stops execution. A shorter interval will make Send more responsive, but provide less CPU time to user code. A longer poll interval will make Send less responsive, but provide more CPU time to user code.

If SendPollInterval is zero, a default value of 1ms is used. The minimum value is 1ms, and the maximum value is 1s.

SendPollIntervalFn allows more fine-grained control of the send poll interval.

SendPollIntervalFn must be a function which takes an iteration number i and returns the delay for the i'th polling interval.

ManualFramingMode controls how the framing headers (Content-Length/Transfer-Encoding) are set for a request.

If ManualFramingMode is true, the request uses the exact framing headers set in the message. If ManualFramingMode is false, or ManualFramingMode is true and the framing is invalid, the framing headers are based on the message body, and any framing headers already set in the message are discarded.

HandoffFanout passes the request through the Fanout GRIP proxy and on to a backend.

This can only be used on services that have the Fanout feature enabled.

The sending completes in the background. Once this method has been called, no other response can be sent to this request, and the application can exit without affecting the send.

HandoffWebsocket passes the WebSocket directly to a backend.

This can only be used on services that have the WebSockets feature enabled and on requests that are valid WebSocket requests. The sending completes in the background.

Once this method has been called, no other response can be sent to this request, and the application can exit without affecting the send.

ResVPNProxyData analyzes the current downstream request's IP address and returns VPN and proxy intelligence data.

Response will return the field "Available" as false if the ResVPNProxy dataset is not enabled for the service.

Example usage:

vpnData, err := r.ResVPNProxyData()
if err != nil {
    return err
}

Send the request to the named backend. Requests may only be sent to backends that have been preconfigured in your service, regardless of their URL. Once sent, a request cannot be sent again.

By default, read-through caching is enabled for requests. The HTTP response received from the backend will be cached and reused for subsequent requests if it meets cacheability requirements. The behavior of this automatic caching can be tuned (or disabled) via the Request's CacheOptions field. This function provides the full benefits of Fastly's purging, request collapsing, and revalidation capabilities, and is recommended for most users who need to cache HTTP responses.

SetBody sets the Request's body to the provided io.Reader. Prefer using this method over setting the Body field directly, as it enables optimizations in the runtime.

If an unread body from an incoming client request is set on an outgoing upstream request, the body will be efficiently streamed from the incoming request. It is also possible to set the unread body of a received response to the body of a request, with the same results.

If the body is set from an in-memory reader such as bytes.Buffer, bytes.Reader, or strings.Reader, the runtime will send the request with a Content-Length header instead of Transfer-Encoding: chunked.