Hi John,
Thanks for all of your help with this issue. I'm still seeing pretty heavy
401s in site streams (about half of the time when I create a connection). Do
you have an approximate timeline on when this fix will be live? For things
where the REST API doesn't suffice, would you recommend
We have a user database lookup capacity issue that is most acute on Site
Streams. This is compounded by a bug that causes Hosebird to cache a
timed-out database lookup as a negative authentication entry, and then your
account can't log in on that one server for the cache duration. Generally if
you
I have been getting sporadic 401s interleaved with 200s while connected to
Site Streams. I'll either open up a connection and it'll return 401s for a
while, then eventually start returning normal responses, or vice versa. This
issue started cropping up yesterday after the Site Stream restarts.
