You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During at least one run, Lighthouse requests URLs that are truncated, apparently after 74 characters (protocol + hostname + path), but with '…' appended (encoded as %E2%80%A6 in the request). This results in a flurry of 404 responses, and, presumably, a questionable lighthouse result. We have observed this with various sites operated by different customers on different platforms on different domains. The site at http://unimportant-site.com/lighthousetest.html is an entirely static copy of one customer site and does not contain '…' as far as I can tell.
Example of one untruncated URL, as well as the truncated version, as requested by Lighthouse on the test site given above, and the (anonymized, but correct length) customer's URL:
Provide the steps to reproduce
What is the current behavior?
During at least one run, Lighthouse requests URLs that are truncated, apparently after 74 characters (protocol + hostname + path), but with '…' appended (encoded as %E2%80%A6 in the request). This results in a flurry of 404 responses, and, presumably, a questionable lighthouse result. We have observed this with various sites operated by different customers on different platforms on different domains. The site at http://unimportant-site.com/lighthousetest.html is an entirely static copy of one customer site and does not contain '…' as far as I can tell.
Example of one untruncated URL, as well as the truncated version, as requested by Lighthouse on the test site given above, and the (anonymized, but correct length) customer's URL:
What is the expected behavior?
No unsolicited modification of URLs.
Environment Information
The text was updated successfully, but these errors were encountered: