Stickiness on req.payload fails

[Miloš Kozák]

Hi,




   4B ... protocol identifier FF00FF00
   1B ... protocol version
   4B ... ID which can be used for stickiness
   4B ... metadata

Having this in mind I decided to define a binary stick-table
|stick-table type binary len 4 size 50 expire 2m|
and stick on derective
|stick on req.payload(5,4)|







Thank you for help, Milos

I am trying to set up a load balancer for a special binary protocol which uses TCP for transport. Each TCP payload starts with sequence of bytes which can be used for load balancing and stickiness. Each packet starts with When ID is 0 everything works, i.e., printing the stick table shows me key=0000 and selected server, and all the communication is sticked to the one selected server. However, when ID is not 0 I never get stick-table entry and each TCP session goes to a different worker according to the roundrobin. I am afraid that it is some kind of a bug because I tried to use string stick table as well without success. Example of a simple communication is enclosed Also, I can provide TCP server and client to generate this kind of communication..

protokol-initiation.pcapng
Description: application/pcapng