Support/Live Chat/Web Client/Kitsune integration: Difference between revisions

Support/Live Chat/Web Client/Kitsune integration (view source)

256 bytes added , 4 May 2010

canmove, Confirmed users

382

edits

@@ Line 3: / Line 3: @@
 ==Step 1: routing traffic (needs IT approval)==
 Ajax requests to a backend server is used for all communication to and from Live Chat.  To satisfy the same-origin policy when embedding chat into Kitsune pages, a proxy needs to be set up to route requests to the backend server.
+===Use Zeus to redirect data (Option 1)===
 Since we have multiple webheads and a single Live Chat server, the simplest network configuration is to use ZXTM to route https://support.mozilla.com/chatapp/ to the Jetty installation at https://chat-support.mozilla.com/chatapp/ .  End-to-end encryption is important as passwords are sent over the link.
@@ Line 11: / Line 13: @@
 * https://chat-support.mozilla.com/chatapp/themes/* (Static CSS)
 * https://chat-support.mozilla.com/chatapp/resource/* (minified resources, not yet implemented)
+===Use a Python proxy (Option 2)===
+We could avoid additional server configuration by configuring Django's built-in proxy to route the Live Chat requests
+* Docs: [http://pypi.python.org/pypi/django-http-proxy/]
 ==Step 2: authentication (existing system for CSAT)==