Location Bar is a widget in a Web user agent's user interface which displays (and often allows input of) the textual location (entered as a URI) of the resource being requested (or displayed - after the response is received).
Web Security Context: User Interface Guidelines ( 版) http://www.w3.org/TR/2010/REC-wsc-ui-20100812/#def-locationbar
[1]
Hacking for Christ: Location Bar Proposal (2007-02-17 12:04:48 +09:00 版) http://weblogs.mozillazine.org/gerv/archives/2007/02/location_bar_proposal.html
(名無しさん2007-02-17 03:07:22 +00:00)
[5] Web Security Context: User Interface Guidelines
( 版)
http://www.w3.org/TR/wsc-ui/#IdentitySignal
User agents MUST make information about the identity of the Web site that a user interacts with available. This [Definition: identity signal ] SHOULD be part of primary user interface during usage modes which entail the presence of signaling to the user beyond only presenting page content. Otherwise, it MUST be available through secondary user interface.
[6]EV SSL も参照。
[7] cURL - How To Use
( ())
https://curl.haxx.se/docs/manpage.html
If you specify URL without protocol:// prefix, curl will attempt to guess what protocol you might want. It will then default to HTTP but try other protocols based on often-used host name prefixes. For example, for host names starting with "ftp." curl will assume you want to speak FTP.
curl will do its best to use what you pass to it as a URL. It is not trying to validate it as a syntactically correct URL by any means but is instead very liberal with what it accepts.
[8]Chrome でアドレスバーを無編集のまま Enter すると、
再読み込みとみなされるのか、 Cache-Control:max-age=0
が付くようです。
[10] Chromium Blog: Moving Towards a More Secure Web
( ())
http://blog.chromium.org/2016/09/moving-towards-more-secure-web.html
Historically, Chrome has not explicitly labelled HTTP connections as non-secure. Beginning in January 2017 (Chrome 56), we’ll mark HTTP sites that transmit passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.
[26] Avoiding the Not Secure Warning in Chrome | Web | Google Developers
()
https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn
たしかに、2004 年ごろに流行したフィッシングの手口では、アドレスバーの上に枠のないウィンドウを乗せる手法により、偽サイト上でアドレスバーに本物サイトのアドレスを表示していました。しかし、これは、Windows XP SP1 (Service Pack 1) の Internet Explorer 6 SP1 を使用した場合に可能なことで、その後にリリースされた Windows XP SP2 や、Internet Explorer 6 SP2 では、そのような偽装ができないよう対策されています。
[28] Google Online Security Blog: Next Steps Toward More Connection Security
()
https://security.googleblog.com/2017/04/next-steps-toward-more-connection.html
[30] 909326 - [UX] Overhaul the site identity and connection information in the identity panel
()
https://bugzilla.mozilla.org/show_bug.cgi?id=909326
[36] 9月の月例更新でInternet Explorerの検索ボックスが復活 | スラド IT
()
https://it.srad.jp/story/17/09/16/024245/
[37] Internet Explorerのアドレスバーに入力した内容をWebページが読み取れるバグ | スラド セキュリティ
()
https://security.srad.jp/story/17/09/30/1832253/
[43] New in Chrome 62 | Web | Google Developers
()
https://developers.google.com/web/updates/2017/10/nic62
[46] Firefox Focus Adds Quick Access Without Sacrificing Users’ Privacy - The Mozilla Blog
()
https://blog.mozilla.org/blog/2017/12/13/firefox-focus-adds-quick-access-without-sacrificing-users-privacy/
[47] Chromium Blog: A secure web is here to stay
()
https://blog.chromium.org/2018/02/a-secure-web-is-here-to-stay.html
Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure”.
[72] Chromium Blog: A safer default for navigation: HTTPS
(, )
https://blog.chromium.org/2021/03/a-safer-default-for-navigation-https.html
[73] Website typo protection defends against fraud including phishing, malware, and other scams - Microsoft Edge Blog, Microsoft Edge Blog, https://blogs.windows.com/msedgedev/2022/10/17/website-typo-protection-typosquatting/