ItEr75S19DeployFrameworkItEr74S08
TWiki>
LibrePlan Web>ItEr75S19DeployFrameworkItEr74S08 (03 Jan 2012, JavierMoran)EditAttach
| Story summary | Deploy framework |
| Iteration | ItEr75week25To52 |
| FEA | ItEr75S19DeployFrameworkItEr74S08 |
| Story Lead | ItEr74S08DeployFramework |
| Next Story | |
| Passed acceptance test | No |
Acceptance Criteria
Additional Specification Comments
Implementation Notes
jMeter cookies issue
The way cookies (containing authentication tokens) are set vary depending on the application server being used. When an user hits the authentication URL and presents login credentials for the first time, two cookies are issued by the server: the anonymous session ID and the authenticated user session ID. Whereas Jetty provides separate Set-Cookie headers for each cookie, Tomcat pushes both tokens within a single header.
HTTP/1.1 302 Found
Date: Tue, 09 Aug 2011 13:35:21 GMT
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: JSESSIONID=t7onkwud0t2r1ep62uww9xqs9;Path=/navalplanner-webapp
Set-Cookie: JSESSIONID=eaz1xhva4f96zi3whlo6z972;Path=/navalplanner-webapp
Location: http://masterplan.libreplan.igalia.com:9901/navalplanner-webapp/;jsessionid=eaz1xhva4f96zi3whlo6z972
Content-Length: 0
Server: Jetty(6.1.24)
HTTP/1.1 302 Moved Temporarily
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=F5644AE4355EF2BBF1B289ECAC308CF8; Path=/navalplanner-webapp
JSESSIONID=E9FC4376392902BC8E25F9CE96EE77C6; Path=/navalplanner-webapp:
Location:
http://masterplan.libreplan.igalia.com:9901/navalplanner-webapp/;jsessionid=E9FC4376392902BC8E25F9CE96EE77C6
Content-Length: 0
In case equal cookies are set in the same header (particularly JSESSIONID), jMeter Cookie Manager stores just the first one, ignoring subsequent assignments. That behavior causes jMeter to store the anonymous token instead of the authenticated user one, causing successive requests to fail as the inappropriate session ID is sent to the server.
A simple way to work around this problem, is to issue an initial GET per client to collect an anonymous session ID first, to ensure that when the user authenticates only one cookie is issued and jMeter doesn't have any trouble storing the proper session ID.
I'm not sure if this should be considered as a bug or a feature. It depends on what HTTP's RFC says about this matter, specifically what the user agent should do if a cookie that was previously set is assigned again while continuing parsing Set-Cookie.
-- NachoBarrientos - 16 Aug 2011
Delay Causes
Final or Pending Considerations
%RPSHOWGITCOMMITS%
| Tasks | Est | Spent | To do | Risk | Reviewer | Developer | Task Name | Start Date | Est End Date | End Date |
|---|---|---|---|---|---|---|---|---|---|---|
| Task | 35 | 35 | 0 | Low | JavierMoran | NachoBarrientos | Stress load tests for the application | 0 | 0 | 0 |
| User | Spent in XpTracker | Spent in phpReport | Ok? |
|---|---|---|---|
| NachoBarrientos | 35 | 0 |  |
| Total | 35 | 0 | |
Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.