ICEpush
  1. ICEpush
  2. PUSH-306

Fix browser ID cookie based setup

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 4.0.BETA, EE-3.3.0.GA_P02
          • Fix Version/s: 4.0.BETA, EE-3.3.0.GA_P02, 4.0
          • Component/s: Push Library
          • Labels:
            None
          • Environment:
            supported browsers

            Description

            When using ICEfaces the browser ID is sent to the bridge in a cookie. The browser ID value will not make into the local storage when setup this way. As a result the ice.push.browser parameter is always empty, for any ICEpush request.

              Activity

              Hide
              Permalink
              Mircea Toma added a comment -

              Make sure the browser ID is sent to the bridge (through the response message) whenever the push request is missing the ice.push.browser parameter value. The check now disregards the presence of ice.sendConfiguration parameter since the browser ID needs to be setup before any extra ICEpush configuration will be sent to the bridge. Previously the, when using local storage in the bridge, the bridge would end up using an empty string as a browser ID.

              Also, modified bridge to read in (to local storage) the browser ID from the cookie to avoid generating extra IDs and skip an extra browser ID configuration response.

              Show
              Mircea Toma added a comment - Make sure the browser ID is sent to the bridge (through the response message) whenever the push request is missing the ice.push.browser parameter value. The check now disregards the presence of ice.sendConfiguration parameter since the browser ID needs to be setup before any extra ICEpush configuration will be sent to the bridge. Previously the, when using local storage in the bridge, the bridge would end up using an empty string as a browser ID. Also, modified bridge to read in (to local storage) the browser ID from the cookie to avoid generating extra IDs and skip an extra browser ID configuration response.

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Mircea Toma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: