{"id":732,"date":"2013-02-01T00:00:00","date_gmt":"2013-02-01T00:00:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2013\/02\/01\/cookiepersist-https\/"},"modified":"2021-07-31T17:52:44","modified_gmt":"2021-07-31T17:52:44","slug":"cookiepersist-https","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html","title":{"rendered":"F5 LTM &#8211; Cookie Persistence between HTTP and HTTPS"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_65 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-661ee47df26c7\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-661ee47df26c7\"  aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#BACKGROUND\" title=\"BACKGROUND\">BACKGROUND<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#SOLUTION\" title=\"SOLUTION \n\">SOLUTION \n<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#Cookie_Types\" title=\"Cookie Types\">Cookie Types<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#Overview\" title=\"Overview\">Overview<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#iRule_Options\" title=\"iRule Options \n\">iRule Options \n<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#Strict\" title=\"Strict \n\">Strict \n<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#Standard\" title=\"Standard\">Standard<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#iRule_Notes\" title=\"iRule Notes\">iRule Notes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#DEPLOYMENT\" title=\"DEPLOYMENT\">DEPLOYMENT<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\/#TROUBLESHOOTING\" title=\"TROUBLESHOOTING\">TROUBLESHOOTING<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"BACKGROUND\"><\/span><strong>BACKGROUND<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available ; Cookie Hashing and Source IP.<\/p>\n<p>In order to perform &#8220;true&#8221; Cookie (insert) persistence across services an iRule is required.<\/p>\n<p><em>Note : Though cookie persistence (insert) can be performed within the cookie persistence profile, this does not allow you to perform persistence across services when the pool members are on different backend ports (i.e HTTP-&gt;80 \/ HTTPS-&gt;81).\u00a0<\/em><\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"SOLUTION\"><\/span><strong>SOLUTION<br \/>\n<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>To maintain persistence across services an iRule is first created. This iRule is then assigned to a Universal Persistence profile which is then assigned to each of the Virtual Servers.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Cookie_Types\"><\/span><strong>Cookie Types<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Before we look at how the iRule(s) work it is worth mentioning the two <em>main<\/em> types of cookies. They are :<\/p>\n<ul>\n<li><strong>Persistent cookie<\/strong> &#8211; A persistent cookie has a date expiration. These cookies display when the cookie will expire under the Expires column (within the browser).<\/li>\n<li><strong>Session cookie<\/strong> &#8211; A session cookie does not have a date expiration set. These cookies display &#8220;session&#8221; under the Expires column (within the browser).<\/li>\n<\/ul>\n<p><em>Note<\/em> : The other types of cookies can be viewed <a href=\"http:\/\/en.wikipedia.org\/wiki\/HTTP_cookie\">here<\/a>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Overview\"><\/span><strong>Overview<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The iRule operates by creating a unique cookie which is provided to the client within the HTTP RESPONSE. This cookie value (UIE key) is also added to a universal persistance record on the F5 which is later referenced for any further HTTP REQUESTS.<\/p>\n<p>Below is an example of a universal persistence record,<\/p>\n<pre class=\"prettyprint&quot;\">root@f5ltm(Active)(tmos)# show ltm persistence persist-records all-properties\r\nSys::Persistent Connections\r\nuniversal - 172.16.100.10:80 - 192.168.1.31:80\r\n-----------------------------------------------------------\r\n\u00a0 TMM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\r\n\u00a0 Mode\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 universal\r\n\u00a0 Key\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8abc87e0260ca1eddb577d37bf4018f5_1359498668\r\n\u00a0 Age (sec.)\u00a0\u00a0\u00a0 6\r\n\u00a0 Virtual Name\u00a0 VS-172.16.100.10-80\r\n\u00a0 Virtual Addr\u00a0 172.16.100.10:80\r\n\u00a0 Node Addr\u00a0\u00a0\u00a0\u00a0 192.168.1.31:80\r\n\u00a0 Pool Name\u00a0\u00a0\u00a0\u00a0 POOL-172.16.100.10-80-A\r\n\u00a0 Client Addr\u00a0\u00a0 172.16.1.1<\/pre>\n<p><em>Note :<\/em> The Age within the persistence record is an idle timeout. Meaning when a persistence look up is performed the Age is reset back to 0.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"iRule_Options\"><\/span><strong>iRule Options<br \/>\n<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Because of the differences in how persistence should be performed there are 2 iRule options available here ; strict and standard.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"Strict\"><\/span><strong>Strict<br \/>\n<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<pre># Name        : Virtual Server Cookie Persistence (strict)\r\n# Purpose     : Cookie Persistence across Virtual Server services\r\n# Methodology : Create cookie containing \"unique\" hash and creation time. \r\n#               This cookie is then used to persist connections.\r\n\r\nwhen HTTP_REQUEST {\r\n\t   \tset cookie_timeout 900\r\n\r\n\t\tif { [HTTP::cookie exists \"b1P\"] } {\r\n\t\t\t# calculate current\/elapsed time \r\n\t\t\tset now [clock seconds]\r\n                        set cookie_epoch [getfield [HTTP::cookie \"b1P\"] \"_\" 2]\r\n\t\t\tset timer [expr {$now - $cookie_epoch}]\r\n            \t\t\r\n\t\t\tif { $timer &gt; $cookie_timeout } {\r\n\t\t\t\t# if cookie timeout is exceeded create new cookie within response\r\n\t\t\t\tset cookie [HTTP::cookie value \"b1P\"]\r\n                                set cookie_check 1\r\n                                #_debug_# log local0. \"[virtual name] [IP::client_addr] TM_EXCEED $cookie 1\"\r\n\t\t\t} else {\r\n\t\t\t\t# if cookie is present and timeout valid then persist\r\n\t\t\t\tpersist uie [HTTP::cookie value \"b1P\"]\r\n                                set cookie_check 0\r\n                                #_debug_# log local0. \"[virtual name] [IP::client_addr] TM_OK [HTTP::cookie value \"b1P\"] 1\"\r\n\t\t\t}\t\t\t\t\t\r\n\t\t} else {\r\n            \t\t# if there is no cookie present add one within the response\r\n\t\t\tset cookie_check 2\r\n\t\t\t}\r\n}\r\nwhen HTTP_RESPONSE {\r\n\t\tset cookie_expiry 900\r\n\r\n\t\t# if cookie timeout is exceeded within request delete persistance entry\r\n\t\tif { $cookie_check eq 1 } {\r\n                        persist delete uie $cookie\r\n                        #_debug_# log local0. \"[virtual name] [IP::client_addr] REMOVE $cookie 1\"\r\n        }   \t\t\r\n\t\t# if cookie timeout exceeded or there is no cookie then create new cookie and add to reponse\r\n\t\tif { ($cookie_check eq 1) or ($cookie_check eq 2)} {\r\n\t\t\t# create hash for cookie\r\n\t\t\tset now [clock seconds]\r\n\t\t        set token \"[IP::server_addr][IP::client_addr][TCP::client_port][expr { int(1000000 * rand()) }]\"\r\n                        binary scan [md5 $token] H* md5var junk\r\n                       \r\n\t\t\t# insert cookie and add expiry\r\n\t\t\tHTTP::cookie insert name \"b1P\" path \/ value $md5var\\_$now\r\n\t\t\tHTTP::cookie expires b1P $cookie_expiry\r\n\t\t\t#_debug_# log local0. \"[virtual name] [IP::client_addr] INSERT [HTTP::cookie \"b1P\"] 1or2\"\r\n                        persist add uie [HTTP::cookie \"b1P\"]\r\n\t\t}\r\n}\r\n<\/pre>\n<p>To ensure that a client session is only persistent for a fixed time period, the strict version is used. This adds an expiry time to the cookie. Unfortunately because not all browsers honour this expiry value, at the point the cookie is created a timestamp (using the EPOCH format) is also appended to the cookie value. This is then used to ensure that if the client sends a cookie that exceeds the timeout the connection is rebalanced.<br \/>\nThis option works well for scenarios when session draining is required.<\/p>\n<p>Within this iRule there are 2 variables that define the timeout. These are :<\/p>\n<ul>\n<li>cookie_timeout &#8211; This value represents (in seconds) the amount of time between the cookie create time (appended EPOCH) and the current time.<\/li>\n<li>cookie_expiry &#8211; This value represents (in seconds) the amount of time in seconds that will be added to the cookie expiry timeout. i.e should this value be set to 900 secs and the cookie create on the 15th April 2012 15:00 then the expiry time will be set to 15th April 2012 15:15.<\/li>\n<\/ul>\n<p><em>Note :<\/em> Both timeouts (by default) are set to 15minutes.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"Standard\"><\/span><strong>Standard<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<pre># Name        : Virtual Server Cookie Persistence (standard)\r\n# Purpose     : Cookie Persistence across Virtual Server services\r\n# Methodology : Create cookie containing \"unique\" hash. This cookie is then used to persist connections.\r\n\r\nwhen HTTP_REQUEST {\r\n\t   if { [HTTP::cookie exists \"b1P\"] } {\r\n                        # if cookie is present then persist \r\n\t\t\tpersist uie [HTTP::cookie value \"b1P\"]\r\n                        set cookie_check 0 \r\n                        #_debug_# log local0. \"[virtual name] [IP::client_addr] PRESENT [HTTP::cookie value \"b1P\"] 0\"\t\r\n\t\t\t} else {\r\n\t\t\t\tset cookie_check 1\r\n\t\t\t}\r\n}\r\nwhen HTTP_RESPONSE { \t\r\n                # if there is no cookie in request then add cookie to response\r\n\t\tif { $cookie_check eq 1 } {\r\n\t\t\t# create hash for cookie\r\n\t\t\tset now [clock seconds]\r\n\t\t\tset token \"[IP::server_addr][IP::client_addr][TCP::client_port][expr { int(1000000 * rand()) }]\"\r\n                        binary scan [md5 $token] H* md5var junk\r\n                        # insert cookie\r\n                        HTTP::cookie insert name \"b1P\" path \/ value $md5var\\_$now\r\n\t\t\t#_debug_# log local0. \"[virtual name] [IP::client_addr] INSERT [HTTP::cookie \"b1P\"] 1\"\r\n                        persist add uie [HTTP::cookie \"b1P\"]\r\n\t\t}\r\n}\r\n<\/pre>\n<p>With this option no expiry time is added to the cookie and the EPOCH timestamp is not referenced. The only value that mandates how long the session is persisted for is the Age value within the universal persistence record. However (as previously mentioned) as this is an idle timeout it can result in the client maintaining persistence to a single server for extremely long periods (i.e until the client stops sending traffic for the length of the universal persistence timeout).<br \/>\nThis option is recommended if the application session also has a idle timeout. This ensures that the application session times out before the persistence record in turn preventing the situation where an existing session is being sent to a (newly balanced) backend server that has no knowledge of the session.<\/p>\n<p><em>Note :<\/em> Based on this you will need to ensure the idle timeout of the persistence record is longer then the idle timeout of the application.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"iRule_Notes\"><\/span><strong>iRule Notes<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>For the iRule jedi`s out there, you may of noticed that in the iRule (standard) there is no logic that covers the event of a cookie being sent, but there being no corresponding persistence entry. In this scenario at the point the F5 performs a &#8216;persist lookup&#8217; and no UIE entry is found then the traffic will be rebalanced and a new persistence entry created.<\/li>\n<li>Though the EPOCH value is not used within the standard option, this value is still appended to the cookie to assist in any troubleshooting that may be required.<\/li>\n<\/ul>\n<h3 class=\"h3\"><span class=\"ez-toc-section\" id=\"DEPLOYMENT\"><\/span><strong>DEPLOYMENT<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>To deploy either of the 2 persistence options follow the steps below:<\/p>\n<p>1. Create an iRule using on of the above options.<br \/>\n2. Create universal persistence profile using the following settings<\/p>\n<pre class=\"prettyprint&quot;\">ltm persistence universal PERSIST-COOKIE-HTTP_S { \r\n\u00a0defaults-from universal \r\n\u00a0match-across-pools disabled \r\n\u00a0match-across-services enabled \r\n\u00a0match-across-virtuals disabled \r\n\u00a0mirror disabled \r\n\u00a0override-connection-limit disabled \r\n\u00a0rule &lt;IRULE NAME&gt; \r\n\u00a0timeout &lt;???&gt; \r\n}<\/pre>\n<p>3. Assign the persistence profile to your Virtual Servers (i.e port 80 and 443).<br \/>\n4. Enable OneConnect on all Virtual Servers that the new persistence profile has been applied to.<\/p>\n<h3 class=\"h3\"><span class=\"ez-toc-section\" id=\"TROUBLESHOOTING\"><\/span><strong>TROUBLESHOOTING<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Should persistence still fail or present problems there are a number of ways that you can troubleshoot. Typically I use a method of obtaining a string within the webpage to determine which server I am connected to. I then use a combination of curl (using the cookie options) and grep to determine if basic persistence is working.<\/p>\n<p>However in circumstances where the issue centres around timeout issues with your persistence session then you can :<\/p>\n<ol>\n<li>Enable debugging within the iRule and remove the #_debug_# syntax for each of the log lines. These logs can then be viewed within \/var\/log\/ltm.<\/li>\n<li>To also log the node that the traffic is sent to\n<ul>\n<li>add the $node variable to the log line<\/li>\n<li>add the following syntax above each log line &#8212; set node [persist lookup uie [HTTP::cookie value &#8220;b1P&#8221;] node]<\/li>\n<\/ul>\n<\/li>\n<li>Add an entry to each log line for any other session cookie values that are being used. So that you can match up the life of the persistence cookie to that of your application session cookie.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>BACKGROUND In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available ; Cookie Hashing and Source IP. In order to perform &#8220;true&#8221; Cookie (insert) persistence across services an iRule is required. Note : Though cookie persistence (insert) can be performed within the &#8230; <a title=\"F5 LTM &#8211; Cookie Persistence between HTTP and HTTPS\" class=\"read-more\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\" aria-label=\"Read more about F5 LTM &#8211; Cookie Persistence between HTTP and HTTPS\">Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>F5 LTM - Cookie Persistence between HTTP and HTTPS - Fir3net<\/title>\n<meta name=\"description\" content=\"BACKGROUND In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"F5 LTM - Cookie Persistence between HTTP and HTTPS - Fir3net\" \/>\n<meta property=\"og:description\" content=\"BACKGROUND In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\" \/>\n<meta property=\"og:site_name\" content=\"Fir3net\" \/>\n<meta property=\"article:published_time\" content=\"2013-02-01T00:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-07-31T17:52:44+00:00\" \/>\n<meta name=\"author\" content=\"Rick Donato\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rick Donato\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\"},\"author\":{\"name\":\"Rick Donato\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037\"},\"headline\":\"F5 LTM &#8211; Cookie Persistence between HTTP and HTTPS\",\"datePublished\":\"2013-02-01T00:00:00+00:00\",\"dateModified\":\"2021-07-31T17:52:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\"},\"wordCount\":970,\"publisher\":{\"@id\":\"https:\/\/www.fir3net.com\/#organization\"},\"articleSection\":[\"F5 Loadbalancers\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\",\"url\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\",\"name\":\"F5 LTM - Cookie Persistence between HTTP and HTTPS - Fir3net\",\"isPartOf\":{\"@id\":\"https:\/\/www.fir3net.com\/#website\"},\"datePublished\":\"2013-02-01T00:00:00+00:00\",\"dateModified\":\"2021-07-31T17:52:44+00:00\",\"description\":\"BACKGROUND In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available\",\"breadcrumb\":{\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.fir3net.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Networking\",\"item\":\"https:\/\/www.fir3net.com\/networking\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Loadbalancers\",\"item\":\"https:\/\/www.fir3net.com\/networking\/loadbalancers\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"F5 Loadbalancers\",\"item\":\"https:\/\/www.fir3net.com\/networking\/loadbalancers\/f5-big-ip\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"F5 LTM &#8211; Cookie Persistence between HTTP and HTTPS\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.fir3net.com\/#website\",\"url\":\"https:\/\/www.fir3net.com\/\",\"name\":\"Fir3net\",\"description\":\"Keeping you in the know\",\"publisher\":{\"@id\":\"https:\/\/www.fir3net.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.fir3net.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.fir3net.com\/#organization\",\"name\":\"Fir3net\",\"url\":\"https:\/\/www.fir3net.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png\",\"contentUrl\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png\",\"width\":390,\"height\":88,\"caption\":\"Fir3net\"},\"image\":{\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037\",\"name\":\"Rick Donato\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g\",\"caption\":\"Rick Donato\"},\"description\":\"Rick Donato is a Network Automation Architect\/Evangelist and the founder of Packet Coders.\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"F5 LTM - Cookie Persistence between HTTP and HTTPS - Fir3net","description":"BACKGROUND In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html","og_locale":"en_US","og_type":"article","og_title":"F5 LTM - Cookie Persistence between HTTP and HTTPS - Fir3net","og_description":"BACKGROUND In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available","og_url":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html","og_site_name":"Fir3net","article_published_time":"2013-02-01T00:00:00+00:00","article_modified_time":"2021-07-31T17:52:44+00:00","author":"Rick Donato","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rick Donato","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html#article","isPartOf":{"@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html"},"author":{"name":"Rick Donato","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037"},"headline":"F5 LTM &#8211; Cookie Persistence between HTTP and HTTPS","datePublished":"2013-02-01T00:00:00+00:00","dateModified":"2021-07-31T17:52:44+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html"},"wordCount":970,"publisher":{"@id":"https:\/\/www.fir3net.com\/#organization"},"articleSection":["F5 Loadbalancers"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html","url":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html","name":"F5 LTM - Cookie Persistence between HTTP and HTTPS - Fir3net","isPartOf":{"@id":"https:\/\/www.fir3net.com\/#website"},"datePublished":"2013-02-01T00:00:00+00:00","dateModified":"2021-07-31T17:52:44+00:00","description":"BACKGROUND In order to to maintain persistence between services (such as HTTP and HTTPS) on a single Virtual Server two persistence methods are available","breadcrumb":{"@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/cookiepersist-https.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.fir3net.com\/"},{"@type":"ListItem","position":2,"name":"Networking","item":"https:\/\/www.fir3net.com\/networking"},{"@type":"ListItem","position":3,"name":"Loadbalancers","item":"https:\/\/www.fir3net.com\/networking\/loadbalancers"},{"@type":"ListItem","position":4,"name":"F5 Loadbalancers","item":"https:\/\/www.fir3net.com\/networking\/loadbalancers\/f5-big-ip"},{"@type":"ListItem","position":5,"name":"F5 LTM &#8211; Cookie Persistence between HTTP and HTTPS"}]},{"@type":"WebSite","@id":"https:\/\/www.fir3net.com\/#website","url":"https:\/\/www.fir3net.com\/","name":"Fir3net","description":"Keeping you in the know","publisher":{"@id":"https:\/\/www.fir3net.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.fir3net.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.fir3net.com\/#organization","name":"Fir3net","url":"https:\/\/www.fir3net.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png","contentUrl":"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png","width":390,"height":88,"caption":"Fir3net"},"image":{"@id":"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037","name":"Rick Donato","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g","caption":"Rick Donato"},"description":"Rick Donato is a Network Automation Architect\/Evangelist and the founder of Packet Coders."}]}},"_links":{"self":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts\/732"}],"collection":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/comments?post=732"}],"version-history":[{"count":0,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts\/732\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/media?parent=732"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/categories?post=732"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/tags?post=732"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}