Not sure if this is a bug with Spring 5.0.3 or a new feature to fix things on my end.
After the upgrade, I am getting this error. Interestingly this error is only on
In my case, the problem was caused by not being logged in with Postman, so I opened a connection in another tab with a session cookie I took from the headers in my Chrome session.