APM iRule Event: insert Cookie after Logon Page

How about LB_SELECTED or SERVER_CONNECTED?

I've already tried that, but it's not working :(

May be this;

when ACCESS_ACL_ALLOWED {
  HTTP::cookie insert name "MyCookie" value "MyValue" path "/"
}

just tried it with Firefox and Safari (cache and cookies cleared), in both browsers I don't get a cookie after login in... any ideas?

How about sending the cookie in the first server response?

The "problem" is that the backend application server only accepts requests when the client already has this special cookie with information about his username, his employee number, etc.

OK, last try, HTTP::cookie is definitely supported in the HTTP_REQUEST_SEND event.

I can confirm that I get no error message regarding syntax or stuff like that, but there's simply no cookie added after accessing the backend server.

I used

when HTTP_REQUEST_SEND {

    clientside {

    HTTP::cookie insert name "meinNeuesCookie" value "abc12345" path "/"

    }

    }

Without "clientside" I get an syntax error...

You may need both, one to insert the cookie to the application server and the other to set the cookie back to the client browser. And some logic avoid the repeat.

when HTTP_REQUEST {
  set flag 0
  if { [HTTP::cookie MyCookie] ne "" }{
     set flag 1
  }
}

when ACCESS_ACL_ALLOWED {
  if { $flag eq 0 }{
     HTTP::cookie insert name "MyCookie" value "MyValue" path "/"
  }
}

when HTTP_RESPONSE {
  if { $flag eq 0 }{
      HTTP::header insert "Set-Cookie"  "MyCookie=MyValue;path=/"
  }
  unset flag
}

Hi kunjan,

thanks for your code, we've tested it but it seems that the cookie gets only inserted at HTTP_RESPONSE, after the server response. Our web application on the backend server checks if our cookie exists on first request, and if not it gives us a different response. After reloading the page in the active browser session, the application has recognized the cookie, which means that the cookie gets inserted after the first request.

As said above, I need to manipulate the first request so that the cookie is already be there when it gets to the web application.

Why do you need the "Set-Cookie" header, what is it for?