Does WebSockets not send InitObject in the InitRequest?

I have an implementation where everything works smoothly with regular Sockets, but as soon as I start using WebSockets for the connection the InitObject of InitRequest is always null. I know it's not a serialization issue because if I bypass that step, the client and server communicate perfectly fine through the WebSockets connection. It's just the InitObject in the InitRequest is always null when WebSockets is used.

Is this the expected result? Should I just work around this and not use initObject for authorizing connections?