Google 是否为 HTTPS ASP.NET 页面编制索引？
我有一个在线应用程序，其所有页面都使用 HTTPS。我有 3 个问题：
Google 是否为 HTTPS 网页编制索引？
我有一个受密码保护的单个 ASP.NET 页面（使用 HTTPS）。密码保护基本上是通过Session对象来实现的。输入正确的密码后，它会隐藏登录面板并显示包含敏感数据的同一页面。此页面是否已被 Google 索引？
我有一个实施了表单身份验证的安全文件夹。文件夹中的所有页面也使用 HTTPS。此文件夹中的页面是否由 Google 索引？
谢谢你的帮助，
尼亚兹
I have an online application that all of its pages use HTTPS. I have 3 questions:
Does Google index HTTPS pages?
I have a password protected single ASP.NET page (using HTTPS). Password protection is basically achieved by a Session object. When the correct password is entered, it hides the login panel and displays the same page which has a sensitive data. Is this page indexed by Google?
I have a Secure folder that I implemented Forms Authentication. All pages in folder use HTTPS as well. Are the pages in this folder indexed by Google?
Thank you for your help,
Niyazi
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果这些页面受密码保护，并且您已正确实施密码保护，那么 Googlebot 就无法访问它们。与任何其他网络客户端一样，他们仍然需要密码，并且据我所知，Googlebot 不会进行任何授权尝试。
另外，需要明确的是，HTTPS 提供加密，而不是身份验证。这意味着数据在服务器和客户端之间是加密的，这确保没有人可以在中途捕获数据并查看或修改它。但是，除非您使用身份验证机制保护对该数据的访问，否则任何人仍然可以查看它。
If the pages are password protected, and you've implemented that correctly, there's no way the Googlebot would be able to access them. As with any other web client, they'd still need the password, and Googlebot, as far as I know, doesn't make any attempts at authorization.
Also, to be clear, HTTPS provides encryption, not authentication. This means that the data is encrypted between your server and the client, which ensures that nobody can catch the data midstream and view or modify it. However, unless you protect access to that data with an authentication mechanism, anyone can still look at it.
我为您提供了部分答案：
1）是的，Google 可以索引 HTTPS 页面
2）对此不确定，但您始终可以将其放入 robots.txt 文件中，以确保它不被索引。
3）如果它落后于表单身份验证，那么谷歌应该无法对其进行索引
I have a partial answer for you:
1) Yes Google can index HTTPS pages
2) Not sure about this but you could always put it in a robots.txt file to make sure it is not indexed.
3) if its behind forms authentication then google should not bea ble to index it