Mercurial > hg > nginx-site

comparison xml/en/docs/welcome_nginx_facebook.xml @ 489:2abd1998a0cc

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
- Added a couple of things about flushing DNS resolver cache
author Andrey Alexeev <andrew@nginx.com>
date Thu, 19 Apr 2012 09:54:55 +0000
parents cfc69ee2f0a0
children 5bb373c6e502
comparison
equal deleted inserted replaced
488:78ab3599e1fe 489:2abd1998a0cc
100 experience. Improve your security. Get the results you expect 100 experience. Improve your security. Get the results you expect
101 with absolutely no redirection." 101 with absolutely no redirection."
102 </listitem> 102 </listitem>
103 103
104 <listitem> 104 <listitem>
105 Try to clear browser data (cache, cookies etc.), e.g. perform 105 If you change DNS settings, clear your DNS resolver cache. On
106 "Clear Browsing Data (Chrome)". Caution: you may be 106 Microsoft Windows it is done with the following command:
107 deleting saved passwords information here, so do it carefully 107 Start > Run > ipconfig /flushdns
108 and check what exact actions you are performing. 108 </listitem>
109
110 <listitem>
111 Clear browser data (cache, cookies etc.), e.g. in Chrome
112 find and click "Clear Browsing Data" (Settings > Under the Hood).
113 Caution: you may be deleting saved passwords information here,
114 so do it carefully and check what exact actions you are performing.
109 </listitem> 115 </listitem>
110 116
111 <listitem> 117 <listitem>
112 Try to check the plugins/extensions you've installed 118 Try to check the plugins/extensions you've installed
113 for use with your browser. It might make sense to re-install 119 for use with your browser. It might make sense to re-install
114 your favorite browser and/or try a different one if possible. 120 your favorite browser and/or try a different one if possible.
115 </listitem> 121 </listitem>
116 122
117 <listitem> 123 <listitem>
118 If cleaning "hosts" file (when applicable), changing 124 If cleaning "hosts" file (when applicable), changing
119 DNS servers to Google Public DNS, or fixing your browser 125 DNS servers to Google Public DNS, flushing DNS resolver cache,
120 configuration have helped, it might be that there's a malware 126 or fixing your browser configuration have helped, it might be
121 somewhere on your PC or around. It makes perfect sense then 127 that there's a malware somewhere on your PC or around.
122 to run a number of checks using your preferred 128 It makes perfect sense then to run a number of checks using
123 anti-virus/anti-malware tools. 129 your preferred anti-virus/anti-malware tools.
124 </listitem> 130 </listitem>
125 </list> 131 </list>
126 </para> 132 </para>
127 133
128 <para> 134 <para>