Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: EE-4.0.0.GA
-
Fix Version/s: EE-4.0.0.GA
-
Component/s: JavaScript Client, Push Library
-
Labels:None
-
Environment:Tomcat, ICEfaces(-EE), Showcase
-
Assignee Priority:P1
Description
Using Showcase and a single browser window I see the Set-Cookie for ice.push.browser pass by more than 10 times. This causes a request to eventually have an ice.pushid with a mismatched ice.push.browser. This doesn't seem to harm normal Push, but it does seem to harm Cloud Push.
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | EE-4.0.0.GA [ 11170 ] |
Assignee | Jack Van Ooststroom [ jack.van.ooststroom ] |
Priority | Major [ 3 ] | Blocker [ 1 ] |
Affects Version/s | EE-4.0.0.GA [ 11170 ] |
Summary | ice.push.browser isn't always send in requests even when it should be known | [Regression] ice.push.browser isn't always send in requests even when it should be known |
Assignee | Jack Van Ooststroom [ jack.van.ooststroom ] | Mircea Toma [ mircea.toma ] |
Assignee Priority | P1 [ 10010 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #43989 | Mon Feb 02 13:13:49 MST 2015 | mircea.toma | |
Files Changed | ||||
![]() |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Removed code in ICEPushResourceHandler that sets ice.push.browser cookie since ICEpush relies only on parameters and XML responses for carrying the browser ID. This seems to be code that was overlooked after the refactoring done for
PUSH-317.