Session \u2014 is a way to identify HTTP clients. The session is strictly linked to IP, User-Agent, and fileless request paths.<\/p>\n\n\n\n
With a new request, Spectr tries to find an existing session for it if no suitable session is found \u2014 creates a new one. A new session is not added to the repository if the request was unsuccessful (the return code is different from 2xx).<\/p>\n\n\n\n
If the session has no active connections and no calls for more than 600 seconds, the session is removed from the storage.<\/p>\n\n\n\n
If the session has been authorized once, then the authorization will not be checked for the next requests (thus, authorization and counting the number of clients for HLS are implemented).<\/p>\n\n\n\n
Each session is characterized by a unique token that can be transmitted with an HTTP setting The session is searched for token, IP, User Agent, path. If a session is not found, a new one is created.<\/p>\n\n\n\n Understanding the sessions is essential to properly configure the content access authorization mechanism in Spectr and Middleware.<\/p>","protected":false},"featured_media":0,"parent":346,"menu_order":2,"comment_status":"open","ping_status":"closed","template":"","meta":{"_links_to":"","_links_to_target":""},"doc_tag":[],"class_list":["post-380","docs","type-docs","status-publish","hentry"],"yoast_head":"\ntoken<\/code> at the first request. If the token is not transferred, it will be generated automatically. With this token, there can be only one session. The token is recorded in a cookie X-Mmxx-Session<\/code>.<\/p>\n\n\n\n