Joshua_Rasnier
Nov 25, 2013Nimbostratus
Cookie persistence or Keepalives
Hi everyone,
Hope someone can shed some light.
Currently I am using a normal irule for a single virtual server as an example below.This virtual server is using custom cookie persistence.
when HTTP_REQUEST {
switch -glob [string tolower [HTTP::uri]] {
"/non-ssl*" {
SSL::disable serverside
pool HTTP-pool
}
"/ssl*" {
pool HTTPS-pool
}
}
}
`
The issue I am finding is that when we browse to the non ssl website, then browse to the ssl website. When we go back to the original website all objects are coming up as 404. I have a feeling its the cookies but I thought that cookies would rewrite everytime it is forced to a new server.
One thing to note is that I found that when the 404 error occurs. Two to three minutes after you are able to refresh the page and it returns to normal operations. Which to me are a sign of keepalives being the issue, but cannot for the life of me think of why.
I was thinking of changing my irule to the following,
`when HTTP_REQUEST {
switch -glob [string tolower [HTTP::uri]] {
"/non-ssl*" {
SSL::disable serverside
persist cookie insert NONSSLCOOKIE
pool HTTP-pool
}
"/ssl*" {
persist cookie insert SSLCOOKIE
pool HTTPS-pool
}
}
}
Basically what I am asking to the more experienced, does this look like a cookie persistence issue or more of a keepalives issue?