![]() It would be nice to know where this arises in Brave interaction flow between hosts entry and Brave exception handling to blocked domain. ![]() Not directly related to this there is some latency which appears variable between hosts file entries and Brave ‘acknowledgement’. This was for a different domain name, not twitter. I saw the last one listed, DNS_PROBE_POSSIBLE, for the first time, I believe, after updating to the current Brave version yesterday,, or the day before. The three exception error messages listed above have been returned from some localhost loopback 127.0.0.1 entry in the hosts file at some point in the last couple of weeks. ![]() I can’t remember what exception was thrown when Twitter was blocked. I have not uncommented the facebook entry in the hosts file however. Please note I also have facebook similarly blocked but that remains blocked. I have checked again today and they are still being served. When I removed the comment an hour or so later Twitter page continued to be served. Twitter had been blocked for some days certainly more than one week.Ī couple of days ago I commented the twitter line in the hosts file with a hash/pound sign. This site can’t be reached ’s DNS address could not be found. The web page at might be temporarily down or it may have moved permanently to a new web address. This site can’t be reached refused to connect. One of the following messages is displayed. No domain response resource (web page) is displayed in the browser. The HTTP request is not sent to the server at the domain. wait until the hosts file changes are activated (10 to 20 min)?ĭomain cannot be reached.However twitter web page still loads into browser. No data on which protocols are supported. Twitter site should not load in browser but does.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |