Serious question: Why is this even up for debate?
-
-
-
serious answer: look at the votes ;)
End of conversation
New conversation -
-
-
if I lived in Colorado I would choose CORS because it's local
#taptherockies - 1 more reply
New conversation -
-
-
Great question! I'd choose CORS w/ caveats. The windows-auth-under-IIS story makes CORS a pia with no spec/std for devs to follow.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
there has to be a door #3
- 1 more reply
New conversation -
-
-
how is this a question in 2016? CORS is the only answer due to security.
-
I had situations as recently as a year ago in which cors did not work
-
JSONP increases the surface area for XSS attacks, especially if you don’t control the the data provider.
End of conversation
New conversation -
-
-
JSONP
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
JWT is not on the menu?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
CORS, of cors!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
.
@wycats xdomain is better in all ways. Although with HTTP2 coming push state removes some of the CORS pain.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
JSONP
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
we are, and CORS
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
GraphQL ofcourse
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
CORS however big issues with self-signed certs in Firefox they will not be fixed.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.