[Pkg-javascript-commits] [sockjs-client] 356/434: Mention SockJS behaviour on browsers blocking third party cookies.

Tonnerre Lombard tonnerre-guest at moszumanska.debian.org
Wed Jan 8 00:47:24 UTC 2014


This is an automated email from the git hooks/post-receive script.

tonnerre-guest pushed a commit to branch master
in repository sockjs-client.

commit 71b38f4086d4c89aabe2ea8abe49c58e2beca5ba
Author: Marek Majkowski <majek04 at gmail.com>
Date:   Sun Feb 26 08:08:40 2012 +0000

    Mention SockJS behaviour on browsers blocking third party cookies.
---
 README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/README.md b/README.md
index 1bab36a..15ce193 100644
--- a/README.md
+++ b/README.md
@@ -336,3 +336,10 @@ There are various browser quirks which we don't intend to address:
  * From SockJS point of view there is nothing special about
    SSL/HTTPS. Connecting between unencrypted and encrypted sites
    should work just fine.
+ * Although SockJS does best to support both prefix and cookie based
+   sticky sessions, the latter may not work well cross-domain with
+   browsers that don't accept third-party cookies by default (Safari).
+   In order to get around this make sure you're connecting to sockjs
+   from the same parent domain as the main site. For example
+   'sockjs.a.com' is able to set cookies if you're connecting from
+   'www.a.com' or 'a.com'.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-javascript/sockjs-client.git



More information about the Pkg-javascript-commits mailing list