I feel this request.getSession().setAttribute("caseID",caseID) is not recommended one and it is tied to a user session, what if the request goes to other publish server, you need to use sticky connections and setup dispatcher configurations. please refer this for more information https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/new-httpsession-on-every-r...
create a sling model called CaseDetails, inside the sling model. you can read the cookie value by using the below code, once you have cookie value assign it to the property.
public String getCaseID()
{
return readCookie(SlingHttpServletRequest slingRequest)
}
private String readCookie(SlingHttpServletRequest slingRequest) {
Cookie[] cookies = slingRequest.getCookies();
if (cookies != null) {
for (Cookie cookie : cookies) {
if (cookie.getName().equals("cased")) {
return cookie.getValue();
}
}
}
}
Create a new component and instantiate data-sly-use.case="com.org.CaseDetails" then in the sightly call case.getCaseID to display cased id on the page.
You need to author this component on the redirected page.
Javascript:
You can not read query string in the JS use API, you need to use plain javascript, put a placeholde on the redirected page something lie this <span id="cased"></span>
In javascript/jquery write logic to read cookie value then if you use jQuery you need to assign cookie value to cased somethig like this
$("cased").text(<cookievalue">)
