Headless did not respond with JSON properties and proper HTTP response code when requesting via a non existing site filter

Headless responds now with a real json response and the correct content type 'application/json'. As this bugfix changes the behaviour, this update is considered potentially breaking. Customers should check their client application whether they rely on the old behaviour.

(CMS-18620)