Open benzman81 opened 3 years ago
@benzman81 are we speaking about Linux images: browsers\edge:XXX
?
oh, sorry, yes.
also server msedge.b.tlu.dl.delivery.mp.microsoft.com is called.
@benzman81 we'll try to investigate. What we install is official Debian distribution of Microsoft Edge.
Some more info, if needed, this is the result for two edge instances manually created.
@vania-pooh for now, we solved it by putting the following into /etc/hosts of the docker host:
127.0.1.1 msedge.b.tlu.dl.delivery.mp.microsoft.com
127.0.1.1 assets.msn.com
127.0.1.1 edge.microsoft.com
127.0.1.1 api.msn.com
127.0.1.1 c.msn.com
127.0.1.1 img-s-msn-com.akamaized.net
Our IT department noticed, that there is a lot of data pulled from servers like assets.msn.com, edge.microsoft.com, img-s-msn-com.akamaized.... and others. This seems to be the update mechanism of Edge. More than 200GB of data was fetched from these servers just for a single day of tests (about 3-4 test runs with each about 4.500 Tests). I can reproduce this by watching the traffic and manually starting an instance of Edge using seleniod by creating the session manually. Currently we use version 89.0 and we know that there are updates available. But we want to stay on a defined version for now. Is there a possibility to turn that update mechanism off?