Any update on this? I'm getting it on a site for certain users/ browsers even though it's all configured correctly as well.
The alerts are very intrusive for a production website when things are configured correctly. Especially with user emails rolling in complaining about getting the error. On May 16, 10:22 am, Dan Webb <d...@twitter.com> wrote: > This does sound like a regression of some kind. We'll get this fixed ASAP. > > On Sat, May 15, 2010 at 3:41 PM, JohnB <johnfakor...@yahoo.com> wrote: > > > Are we really talking about incorrect installations here? Twitter's > > own @Anywhere documentation page (http://dev.twitter.com/anywhere/ > > begin) is throwing this same error in older browsers, including Chrome > > 3.0.195. > > -- > Dan Webb > Front-end Engineer, Platform > d...@twitter.com / @danwrong+1 415 425 5631
