SSO for webserver

Yes, chunking is a way of breaking messages up into smaller pieces. It's generally used to facilitate streaming data where you may not know in advance what the total payload size will be or if you want page content to start rendering before all of the data is sent (or generated). The above iRule tells the server that the client cannot handle chunking, by essentially disabling HTTP 1.1. It also tells the server not to compress the response. If you suspect that chunking is still happening, observe the response data in the capture. By the way, you may have a better time by at least analyzing the TCPDUMP data in Wireshark, if not capturing it there. Chunking will be evident by the "Transfer-Encoding: chunked" header. You may also notice whether or not the payload looks compressed (unreadable).

 

 

As for the Form SSO settings, you need to find at least one event that is unique to a successful logon. You're best bet again is to capture that process (I recommend Fiddler of IEWatch in the browser, but also Wireshark) to see what happens directly before and directly after a successful logon. You can attach that capture here if you'd like us to take a look.