Forum Discussion
albert_forster_
Nimbostratus
Nimbostratusrelate_client & relate_server
We use TCP::collect and TCP::payload to gather the initial OPTIONS command. Then use TCP::respond to send an options response back to the client. With TCP::collect and TCP::payload we get the DESCRIBE...
I think the problem with the OPTIONS command is that the command is still in the buffer. So, when you do eventually get the "transid" string, both the OPTIONS and the DESCRIBE end up going to the server.
What you likely will want to do is remove the OPTIONS command after you have responded. You can do this with a command like:
TCP::payload replace ""offset and length indicate the location to replace with the empty string. You may be able to simply throw away the entire payload at the point you determined it was an OPTIONS command. That can be done with:
TCP::payload replace 0 [TCP::payload length] ""
