New JSESSION ID for every server request of single user session
We have noticed that pega is generating new JSESSION ID for every single server request from a pega web browser of a single user session. Also, we noticed that Pega-RULES session ID is remaining constant throughout the user session.
Is this an expected behavior(JSESSION ID getting changed for every server request)? If so, what is the rational behind having the JSESSION ID changed and Pega-RULES session id remaining constant?
Also, we have option to configure the JSESSION ID in the app server settings while we don't have any setting related to Pega-RULES session id. How is pega-Rules session ID managed?