Likely the initial blocklist, safebrowsing and tracking protection updates.
You can add a bool browser.safebrowsing.debug in about:config and set it to
true. You should see some additional messages during start in the console then.
FRG
Richmond wrote:
There is a thread in the firefox group about firefox connecting to
cloudfront. While looking into that I checked on seamonkey and I see the
same:
tcp 0 0 192.168.1.3:54212
server-54-192-129-202.ams50.r.cloudfront.net:https ESTABLISHED 2341/seamonkey
tcp 0 0 192.168.1.3:50642
server-54-192-185-116.cdg51.r.cloudfront.net:https ESTABLISHED 2341/seamonkey
tcp 0 0 192.168.1.3:47018
ec2-54-68-119-170.us-west-2.compute.amazonaws.com:https ESTABLISHED
2341/seamonkey
This is a new profile and I have set the home page to blank. These
connections are made when I launch seamonkey before I do anything else.
What are they about? Is it copies from firefox core code?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
