powered by Jive Software

Openfire websocket plugin - returning HTP status code 302

I thought I’d give the websocket plugin a go. The good news is that it’s pretty trivial to install - no configuration required!

One thing I thought I’d highlight though - I spent ages wondering why I was seeing an HTTP response code 302 coming back from the server.

It turns out that specifying a WS endpoint of http://server:7070/ws is not sufficient - it should be http://server:7070/ws/ - note the trailing slash.

It’s pretty obvious once you’ve figured it out, and I’m kicking myself for taking so long to do so, but I’m just posting this here in case someone else suffers from the same problem,



1 Like