What is supposed to happen is the relay sends AUTH as the very first message. Some clients will ignore this and send a REQ or EVENT. In that case, it sends the proper close or true=false, and another AUTH. It continues to repeat this pattern until the AUTH response has been received. Then it will allow REQs and EVENTs.. I have not seen it fail to send the subscription results, typically this is a race condition in the client.

I would be happy to fix this if it's a bug, but I'm going to have to write another test suite to confirm what you're saying because it seems to work just fine for my client and the other clients I've tested. I have also verified using wireshark the sequencing of the websocket messages.