GoogleChrome/lighthouse

Canonical URL audit mistakes invalid URLs for relative ones

Open

#12,008 创建于 2021年1月26日

在 GitHub 查看
 (7 评论) (0 反应) (0 负责人)JavaScript (27,768 star) (9,278 fork)batch import
P3good first issue

描述

Provide the steps to reproduce

  1. Run LH on https://output.jsbin.com/vulerujohi for just the canonical audit

What is the current behavior?

The audit fails with explanation Relative URL (https:// example.com)

What is the expected behavior?

The audit fails with explanation Invalid URL (https:// example.com)

Environment Information

  • Affected Channels: CLI, Node, DevTools
  • Lighthouse version: 7.0.1
  • Chrome version: 88.0.4324.96
  • Node.js version: 14.15.4
  • Operating System: macOS Mojave 10.14.6

贡献者指南

技术栈
javascriptnodejs
领域
frontendperformance
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
familiarity with Lighthousebasic JavaScript
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
85
研究方向
The issue is that the canonical URL audit incorrectly labels a URL with a space after 'https://' as 'Relative URL' instead of 'Invalid URL'. The fix is to locate the audit logic, likely in `lighthouse core/audits/seo/canonical.js` or similar, find the condition that outputs 'Relative URL', and change it to 'Invalid URL'. The test file for this audit should also be updated to reflect the corrected message.