That aside, I can't really see what can go wrong - deliberately - with a simple DNS name resolution. But since root servers are 0wned, you may have a point in wanting to inpect DNS chatter. It maybe worthwhile not to assess the browser, but to assess DNS infrastructure. Then again, testing DNS infrastructure is a different case that should be isolated from browser tests, I think.
As for direct IP addressing, it should be straightforward to filter out DNS
queries and responses from the chatter, so access by domain names should be
tolerable - as long as you filter DNS part from the chatter. But then, since
you include DNS chatter to the test case, that means you also want to inspect
that. And this adds up to the work you're carrying on.
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser Mason Hock
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser ar018
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser studio
- Re: [Trisquel-users] Web Browser studio