GlobalResponseFilters not working if response is null

ServiceStack
1

In my service I have global response filter. But after upgrade to v. 4.0.46 I see that in some cases it not working.
After checking I discovered that global response filter is not called if response is empty (null).

But I think that global response filter should be called always (because for example we want to add custom headers to all responses).
In my API I’m returning empty responses (with http 200 status code) for http delete requests.
So how to add custom headers in this case ?

2

You can override OnAfterExecute() in your AppHost.

I’ll look at allowing null responses in GlobalResponseFilters.

3

Global Response Filters should now be fired for null responses from this commit.

This change is available from v4.0.47 that’s now available on MyGet.

4

Great - it works. Thank you.
BTW do you publish somewhere PDBs files for pre-release version ?

5

No, not for pre-release packages.