You are missing the point. That code works fine if the Data was gathered from loading an HTTP webpage; it will provide the html as desired. But if the page loaded was from HTTPS then Data will be encrypted preventing you from getting at the html. Thanks for replying.

So, this seems odd to me. If I can't get at the data to help make a decision on filtering then what is the point of this method? Per the documentation,      * @method filterDataVerdictWithFilterInbound:peekInboundBytes:filterOutbound:peekOutboundBytes:      * @discussion This class method returns a new flow verdict indicating that the filter needs to make a decision about      * a new flow after seeing a portion of the flow's data. But in many cases you can't see the data because it's encrypted. My expectation was that the data could be seen. This implies that we can only filter KNOWN bad web pages and we can't filter based on what is in a page. Not very useful. Thanks Matt. I do appreciate you insight.