In our environment, cookies are used heavily for authentication and sessions. Huge cookies from Keycloak, LtpaTokens, JSESSIONID’s, sametimeJwt tokens and stuff from other subdomains.<\/p>\n
Once the Request Header goes over 8k in size, Orient-Me fails to load suggestions stuff. Or “Could not load the activity stream. The request timed out” is a typical message.<\/p>\n
Why does it happen?<\/strong> The Component Pack (<=7.0.2) uses a Node.js version where the max header size is set to 8k.\n\n\nWorkaround<\/strong> Inside my ihs config I added this to remove the sametimeJwt cookie from the requests.<\/p>\n This will remove the cookie from the proxy request to the componentpack.<\/p>\n","protected":false},"excerpt":{"rendered":" In our environment, cookies are used heavily for authentication and sessions. Huge cookies from Keycloak, LtpaTokens, JSESSIONID’s, sametimeJwt tokens and<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[62,54,23],"tags":[],"class_list":["post-773","post","type-post","status-publish","format-standard","hentry","category-62","category-component-pack","category-connections"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
\nUntil the Node.js versions in the componetpack have been upgraded I use the following as a workaround.<\/p>\n
\nSetEnvIfNoCase Request_URI \"^\/appreg.*\" noCookie
\nSetEnvIfNoCase Request_URI \"^\/community_suggestions\/.*\" noCookie
\nSetEnvIfNoCase Request_URI \"^\/social\/.*\" noCookie
\nSetEnvIfNoCase Request_URI \"^\/itm\/.*\" noCookie
\nRequestHeader edit* Cookie \"^(.*?)sametime[jJ][Ww][Tt]=.*?(?:$|;)(.*)$\" $1$2 env=noCookie
\n<\/code><\/p>\n