I have an Azure service bus relay that exposes an on-premise service to external clients. If I hit the on-premise service directly with a particular request (a REST request for resource that doesn't exist), I get a 'HTTP/1.1 204 No Content' response which I like.
When the same request is fired via the Azure relay, a 'HTTP/1.1 502 Bad Gateway' which I don't like because the client code treats this as an error (whereas it silently ignores a 204).
Any suggestions?