[
https://issues.apache.org/jira/browse/FELIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5812:
------------------------------------
Affects Version/s: http.bridge-3.0.18
> External session id differs from internal session id
> ----------------------------------------------------
>
> Key: FELIX-5812
> URL: https://issues.apache.org/jira/browse/FELIX-5812
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
> Affects Versions: http.base-3.0.18, http.jetty-3.4.8, http.bridge-3.0.18
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: http.base-4.0.0, http.jetty-4.0.0, http.bridge-4.0.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
