# WIP: Start auditing all \`forward_request\` calls on the server · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/331667c00e076dbfdb31bbed2be38b1f4818296c)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 331667c00e076dbfdb31bbed2be38b1f4818296c

Requested commit: 331667c00e076dbfdb31bbed2be38b1f4818296c

Commit: 331667c00e076dbfdb31bbed2be38b1f4818296c

Tree: de1b45f7c3d61e0a432a945a6790db94f9128303

Author: Antonio Scandurra

Committer: Antonio Scandurra

## Message

```
WIP: Start auditing all `forward_request` calls on the server

When the host returns an error after a server has forwarded a request,
we want to surface that error to the guest. At the moment, the server
just returns early leaving some requests unresponded on the guest.

I started auditing all the code paths where we do that, but I am
wondering whether there's some other approach that would prevent us
from repeating this mistake in other code paths.

```

## Parents

- [2dbea2804c1e78ac77f8b0caa37bb48d0b5675ac](https://git.cafe/gitcafe/zed/commit/2dbea2804c1e78ac77f8b0caa37bb48d0b5675ac?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/331667c00e076dbfdb31bbed2be38b1f4818296c?format=markdown)
