---
title: bereq.between_bytes_timeout
summary: null
url: >-
  https://www.fastly.com/documentation/reference/vcl/variables/backend-connection/bereq-between-bytes-timeout
---

**Type:** RTIME  
**Access:** can be read and set, but not unset

**Available in:** pass, miss

The amount of time Fastly will allow between reads of HTTP response data sent from the backend, before triggering a timeout. This behaves as a single-request override for the backend `.between_bytes_timeout` setting.

May be set to any value between `0` and `600s`. By default, the timeout is `15s`.

If the timeout is triggered, Fastly will create an error object and invoke `vcl_error` with `obj.status` set to `503` and `obj.response` set to `"between byte timeout"`.  [Learn more about errors](https://www.fastly.com/documentation/guides/concepts/errors).

## Effects of shielding

The timeout between POPs in a shielding arrangement is affected by the settings in each case because the full VCL configuration is executed at each POP separately. For example, to set a timeout that applies only when connecting to the origin and not when connecting to an upstream shield POP, use the following VCL:

```vcl context="sub vcl_miss { ... }"
if (req.backend.is_origin) {
  set bereq.between_bytes_timeout = 10s;
}
```

To configure a specific timeout when connecting to a shield POP:

```vcl context="sub vcl_miss { ... }"
if (req.backend.is_shield) {
  set bereq.between_bytes_timeout = 10s;
}
```
