Functional cookies
A list of the functional cookies used on this site
Cookie
Cookie
Purpose
Purpose
Expiry
Expiry
.ASPXAUTH
Purpose
my.blood.co.uk - This gets created after the donor is logged in the blood donor application and this tells whether the donor is logged in or not.
Expiry
cookies are deleted on browser closure unless the browser settings over rule this
__RequestVerificationToken
Purpose
my.blood.co.uk - Donor Portal application is based on MVC4 and this is feature provide by that platform. This generates a code when application is loaded in the client browser and send back to server for verification.
Expiry
cookies are deleted on browser closure unless the browser settings over rule this
ASP.NET_SessionId
Purpose
my.blood.co.uk - The donor portal application times out after a period and so the user has to login again and reset the cookie. It's self managing in that it persists until the browser closes
Expiry
It's self managing in that it persists until the browser closes. Removal of the sessionid cookie will end an authenticated session and the user will have to login again
JSESSIONID
Purpose
.nr-data.net - The JSESSIONID cookie is used to store a session identifier so that New Relic can monitor session counts for an application. The cookie value is generated by Jetty.
Expiry
https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/new-relic-cookies-used-browser
sf
Purpose
my.blood.co.uk - If a donor portal user does a location search before signing in this cookie is created.
Expiry
The cookie is deleted on browser closure and stores data about the session performed e.g. town or post code. This enables the portal to continue a search after login. This can be deleted via the browser or operating system tools if needed.
nhsbt_user_cookie
Purpose
my.blood.co.uk - If a Donor Portal user wants their user name to be remembered for sign in, it is stored in the cookie
Expiry
Stored for 1 year after creation