I work for a web filtering company that is trying to create a browser that filters specific categories of content that the user selects. So far I have a browser application that is using the XPCOM interface for the embedded component to implement a full browser, but one of the problems I am having is that my filter sits too high in the download process, for it to be accurate.
I need to have my filter sit at a level where it sees all http requests before they hit the socket. The reason I have to sit so low, is that many of the porn sites use re-directs to pay other sites for their listings. At the XPCOM embed level I can only see the original URL, I never see any of the URL's that are downloaded as a result of a redirect. I have been reading up on the architecture of necko, and I am unsure of where the best place would be to insert my filter. Any suggestions? _______________________________________________ Mozilla-netlib mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-netlib
