http-on-modify-request happens before DNS resolution is started. onStartRequest happens after DNS resolution happened (and after the HTTP server has replied to the request). But inserting a stream listener into arbitrary channels is not trivial.
You could try overriding the DNS service contract ID and intercept the calls that way. -christian On Mon, Jul 21, 2008 at 5:41 PM, Doug Turner <[EMAIL PROTECTED]> wrote: > Not without adding this notification which is probably not a bad idea > > If you are only worried about http traffic, you could hook into "http- > on-modify-request". This is called right before HTTP is going to > write to the socket and after the DNS resolution has occurred. You > could then also add a stream listener for all loads. The > onStartRequest would be your indication a DNS resolution may be > occurring soon with the given URI. Not very clean and no way to > prevent the resolution, but it should get the job done. > > Doug Turner > > > > > On Jul 21, 2008, at 6:28 AM, mhand wrote: > >> Is it possible to know when the "dns service" starts and finished to >> resolve a domain name? by adding an observer for example? >> _______________________________________________ >> dev-tech-network mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-tech-network > > _______________________________________________ > dev-tech-network mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-network > _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
