由于有太多全新的网络功能在 HTTPS 上受限制，Paul 和 Jake 探讨了对 HTTPS 是否是网站开发者的合理要求。
2.3. HTTPS 无处不在
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-25。"],[],["Paul and Jake discuss the growing trend of gating new web features behind HTTPS. The core of their discussion revolves around evaluating if mandating HTTPS is a fair expectation for web developers. They delve into the implications of this requirement and whether or not the benefits of secure connections outweigh the potential challenges for developers.\n"]]