Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Avatar for Username

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Ова тема је архивирана. Питајте друго питање ако вам је потребна помоћ.

Connect to remote Websocket from localhost doesn't send cookies

  • 1 одговор
  • 1 има овај проблем
  • 1 преглед
  • Последњи одговор послао cor-el

[e]Bu$ter
[e]Bu$ter
more options

Hi, I am web developer. App I am working on need to connect to remote host by webscoket and send auth cookies to it (aws guard). The problem is when I run app on the local host (dev mode), it works fine in every Chrome based browser, and even Safari, but unable to connect in FF.

For example, my app runs on localhost:8080, and Websocket host is ws.dev.myapp.com For successeful coonection, handshake request should include cookies from .dev.myapp.com domain, or even .myapp.com. So, you can see on screenshots, cookies not included on request from localhost, and we get 403 error instead of 101 on second pic.

I guest this is some secutiry setting I can tweak, but I can't see what exactly. Or can it be a bug?

Hi, I am web developer. App I am working on need to connect to remote host by webscoket and send auth cookies to it (aws guard). The problem is when I run app on the local host (dev mode), it works fine in every Chrome based browser, and even Safari, but unable to connect in FF. For example, my app runs on localhost:8080, and Websocket host is ws.dev.myapp.com For successeful coonection, handshake request should include cookies from .dev.myapp.com domain, or even .myapp.com. So, you can see on screenshots, cookies not included on request from localhost, and we get 403 error instead of 101 on second pic. I guest this is some secutiry setting I can tweak, but I can't see what exactly. Or can it be a bug?
Приложени снимци екрана

Сви одговори (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Maybe the problem is "origin: http://localhost:8080" in the first screenshot (i.e. not coming from a secure connection).

Maybe try to ask advice on a web development oriented forum.