Utilisation

Name Description Conservation Duration
_ga These cookies are used to collect information about how you use our website. The information collected includes number of visitors, pages visited and time spent on the website. The information is collected by Google Analytics in aggregated and anonymous form, and we use the data to help us make improvements to the website. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance. 2 years
_gid These cookies are used to collect information about how you use our website. The information collected includes number of visitors, pages visited and time spent on the website. The information is collected by Google Analytics in aggregated and anonymous form, and we use the data to help us make improvements to the website. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance. 24 hours
_gat_gtag Used to throttle request rate. 1 minute
connect.sid Used to distinguish session. Expires when you exit the browsing session
cookieCompliancyAccepted Used to check if user already accept cookieCompliance 1 year
heroku-session-affinity How it works Heroku’s session affinity mechanism has the following properties: The effect of a dyno joining or leaving the entire set of dynos for an app is minimized. A dyno being unresponsive causes no downtime to the client. The request is routed to a different dyno. It is portable across applications and requires no modifications to the application, no matter the platform or language. It works on arbitrary clients behind arbitrary ISPs or infrastructure, as long as they support HTTP cookies. The requirement for HTTP cookies is there because it has been judged the most reliable and least invasive means by which to offer session affinity (compared with other means such as IP addresses or URL-based mechanisms). As soon as the feature is enabled on an application, the Heroku router will start adding an HTTP cookie named heroku-session-affinity to every new request and response. This cookie contains no private application information and doesn’t require request- or response-related data to function. Based on this cookie value, the Heroku router will be able to determine the appropriate dyno for each request. The Heroku router will also be able to know when new dynos have been added to the fleet, so that when a scale-up event happens, instead of ending in a scenario where all dynos but the new one serve requests, a fraction of all of them will be moved to occupy the new dyno. If 4 dynos are each holding 10 connections and a 5th dyno is added, you should therefore expect roughly 2 connections (on average) from each existing dynos to be shifted to the 5th dyno to make sure all resources are used equally. The opposite is also true. When a dyno goes away, its connections randomly get redistributed to other available dynos, giving a roughly equal redistribution. 24 hours
Je refuse Compris
Ce site utilise des cookies. Plus d'informations