Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report not downloaded when site is accessed using IP address #5633

Closed
swejaljain opened this issue Jul 9, 2018 · 11 comments
Closed

Report not downloaded when site is accessed using IP address #5633

swejaljain opened this issue Jul 9, 2018 · 11 comments

Comments

@swejaljain
Copy link

Bug report

Provide the steps to reproduce

  1. Add lighthouse as chrome's extension.
  2. Access the web application with server's IP.
  3. Open the chrome's console
  4. Go to Audit Tab and start lighthouse scanning.
  5. Report is displayed in the console.
  6. Click on the download report icon but nothing happens.
    P.S. If the same site is accessed on local machine with localhost using the same steps then report json is downloaded successfully.

What is the current behavior?

Report is nor downloaded on click of download report icon when web application is accessed with server IP.

What is the expected behavior?

Report should be downloaded on click of download report icon despite of the url.

Environment Information

  • Lighthouse extension version : 3.0.1
  • Operating System: windows
  • Chrome version : Version 67.0.3396.99

Related issues
None

@patrickhulce
Copy link
Collaborator

I have no problem downloading a report for a server IP, we have reports of the JSON just not downloading sometimes though (#5638 #5047) perhaps its being flaky?

@patrickhulce
Copy link
Collaborator

Also FYI, the Chrome Extension is accessed separately. Your step description indicates you're actually using v2.9 of Lighthouse built-in to DevTools. Does everything work as expected if you use v3 in Chrome Canary?

@swejaljain
Copy link
Author

Oh yes that's the mistake at my end I just got confused in extension and the built in dev tool. I am facing this issue every time when I am downloading the report from chrome console [you are right I am using v2.9 built in lighthouse]. I haven't check this on v3 in Chrome Canary will check and update.

@swejaljain
Copy link
Author

I have tried the same on v3 in Chrome Canary but again the results are same on using localhost I am able to download the report json but on changing the localhost to IP report is not downloaded. I am not sure what is going wrong in my case. :(

@patrickhulce patrickhulce changed the title Report of lighthouse [chrome extension] is not downloaded from chrome's console when any site is accessed using IP address, report is downloaded when the same site is accessed via localhost. Report not downloaded when site is accessed using IP address Jul 10, 2018
@patrickhulce
Copy link
Collaborator

Hm, it might be Windows specific then. I'm not able to reproduce on Mac. We'll have to look into it.

@justinribeiro
Copy link
Contributor

@patrickhulce I fired up a VM and I can reproduce this on Windows 10 in M67/ LH2.9.1 for one specific case that I believe potentially matches the above. Windows appears to have an issue with an ip address with a host port (x.x.x.x:nnnn); this doesn't throw an error in while debugging, but it never pops the Save As... dialog.

image

A plain no-port IP address appears to work fine, though the colon in other instances also causes odd behavior. As an example localhost:8081 causes the save dialog to remove the localhost:

image

This is likely because filenames in Windows can not have colons (it's a reserved character, per docs).

@patrickhulce
Copy link
Collaborator

Awesome thanks so much for digging in @justinribeiro! 👍

@patrickhulce
Copy link
Collaborator

CL is up :) https://chromium-review.googlesource.com/c/chromium/src/+/1132136

aarongable pushed a commit to chromium/chromium that referenced this issue Jul 10, 2018
BUG=GoogleChrome/lighthouse#5633

Change-Id: I58fc3d6541bfab6305936f5e5f5034b4bcfdaae1
Reviewed-on: https://chromium-review.googlesource.com/1132136
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Patrick Hulce <phulce@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573937}
devtools-bot pushed a commit to ChromeDevTools/devtools-frontend that referenced this issue Jul 10, 2018
BUG=GoogleChrome/lighthouse#5633

Change-Id: I58fc3d6541bfab6305936f5e5f5034b4bcfdaae1
Reviewed-on: https://chromium-review.googlesource.com/1132136
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Patrick Hulce <phulce@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#573937}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: b9e6f065c035bfd0487695bd981cdf57108e5ceb
@swejaljain
Copy link
Author

Thank you so much for your quick responses and resolutions @patrickhulce @justinribeiro :) :)

babot pushed a commit to binaryage/dirac that referenced this issue Jul 11, 2018
BUG=GoogleChrome/lighthouse#5633

Change-Id: I58fc3d6541bfab6305936f5e5f5034b4bcfdaae1
Reviewed-on: https://chromium-review.googlesource.com/1132136
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Patrick Hulce <phulce@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573937}
@wardpeet
Copy link
Collaborator

@swejaljain it's fixed in latest canary.

@swejaljain
Copy link
Author

@wardpeet thank you for the fix :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants