Robson
|
QuakeJS
07-04-20, 01:06
#1
|
||||
Trooper
|
07-04-20, 10:30
#2
Muito legal a ideia!
Da pra brincar, usar alguma cfg? |
Trooper
|
07-04-20, 11:13
#3
pena que meu ping fica mais alto do que qdo joga qwtf com o meu USROBOTICS 33.6k
|
Trooper
|
07-04-20, 16:28
#4
Hahahahah que dahora !!
|
Robson
|
07-04-20, 16:53
#5
Quote:
Hoje temos o HTTP CORS, talvez tenha o análogo de WebSocket |
|
Trooper
|
07-04-20, 18:15
#6
websocket nao tem essas "limitações". é ffa
|
Robson
|
08-04-20, 11:14
#7
Boa. Fui até aprender um pouco mais. Cabe ao server cuidar disto.
https://en.wikipedia.org/wiki/WebSoc...considerations "Unlike regular cross-domain HTTP requests, WebSocket requests are not restricted by the Same-origin policy. Therefore WebSocket servers must validate the "Origin" header against the expected origins during connection establishment, to avoid Cross-Site WebSocket Hijacking attacks (similar to Cross-site request forgery), which might be possible when the connection is authenticated with Cookies or HTTP authentication. It is better to use tokens or similar protection mechanisms to authenticate the WebSocket connection when sensitive (private) data is being transferred over the WebSocket.[38] " |
|
|