304 response in Azure Service Bus relay

Question

I have a request that contains a If-None-Match header that I then compare to the calculated response on the service. If they match and the response hasn't been modified since last I return an empty 304 response.

All this works fine as my content rarely changes but I like to check for changes often.

This however seems to become a problem when exposing the service resource via Service Bus Relay. I don't receive a response at the relay endpoint when sending of a 304 from the service.

Is this a known problem? Is there a way around it as you see it?

Answer 1

This appears to be a bug in ServiceBus Relay. When your listener is returning 304 (or 204) make sure the HttpResponseMessageProperty..StatusDescription is null before sending the response back through SERVICEBUS and that should work-around this issue.