[FELIX-5812] External session id differs from internal session id

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: http.base-3.0.18, http.jetty-3.4.8, http.bridge-3.0.18
• Fix Version/s: http.base-4.0.0, http.jetty-4.0.0, http.bridge-4.0.0
• Component/s: HTTP Service
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 20/Mar/18 10:05
• Updated: 30/Apr/18 08:11
• Resolved: 20/Mar/18 10:11

Description

With the addition of the http whiteboard support, the session id returned is the session id from the container plus the internal context id. As the http whiteboard manager needs to manage different contexts within the context from the container, the session objects need to be different as well. Therefore the implementation is currently using a different id for each of these sessions.

However, this creates a difference between the internal session id and the one from the container and might lead to problems with session replication solutions or even creating links containing the session id as this session id is unknown to the container.

There is nothing in the specification preventing us from using the same session id for different sessions. As all of these are bound to the same container session with the same id, this should be fine and avoids the problems mentioned above.