Azure service bus relay converts 204 'No Content' responses into 502 'Bad Gateway'

Question

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?

Try using Microsoft.ServiceBus.dll version 2.3 with Azure SDK 2.3 — Brian from state farm, Apr 22 '15 at 01:18
Thanks, but we are already using 2.4. I will think about 2.5 though, it might be worth trying. — user381624, Apr 23 '15 at 02:59

score 0 · Answer 1 · answered Feb 08 '16 at 15:36

0

An ugly way could be manually redirecting the non-existing content to a custom 204 message page, haven't tested this and best case would be a temporary solution until you can get the proper response to work.

answered Feb 08 '16 at 15:36

Melis

111
9

There is no web page, this is service / api. – user381624 Feb 14 '16 at 00:31

Azure service bus relay converts 204 'No Content' responses into 502 'Bad Gateway'

1 Answers1