Launch as http://localhost instead of http://127.0.0.1? about vscode-livepreview HOT 6 OPEN

Currently, there is no setting for opening the preview on localhost. Are you using an endpoint that only allows access from the localhost domain name? And if so, are there no workarounds with this?

If you're hosting locally, there are options in livePreview.httpHeaders to modify headers (and potentially the CORS headers) if that helps in your case for consumption.

from vscode-livepreview.

Currently, there is no setting for opening the preview on localhost.

Bummer. Well at least now I know not to look for something that isn't there!

Are you using an endpoint that only allows access from the localhost domain name? And if so, are there no workarounds with this?

It's not that the resource (FontAwesome in particular) only allows access from localhost, but that it only allows access any domain specified. Attempting to specify an IP address doesn't work. Since there's no direct reference (that I can find) to that restriction in their docs, I'm attaching a screen shot. I'm not aware of any workarounds.

If you're hosting locally, there are options in livePreview.httpHeaders to modify headers (and potentially the CORS headers) if that helps in your case for consumption.

Thanks - I'll try that to see if I can get it to work.

from vscode-livepreview.

If you're hosting locally, there are options in livePreview.httpHeaders to modify headers (and potentially the CORS headers) if that helps in your case for consumption.

Wait, my understanding is that these options, as you have in the help for the settings, modify "The extra HTTP headers that should be set in the server's HTTP responses." So these headers impact what the browser sees when requesting resources from the local host, ie http://127.0.0.1:3000.

What I need to manipulate is what Referer is specified when the browser then requests an outside resource (ie. AJAX or script source). In other words, Request Headers, not Response Headers. I'm attaching another screen grab from Firefox's console.

If the extension merely allowed launch on localhost in addition to the specific IP, I wouldn't need to manipulate those headers, they would just be there. I've been using Live Server instead as a result of this requirement.

Totally understand if you don't want to match that requirement! As I mentioned above, more importantly I wanted to make sure I wasn't spending time looking for an option that didn't exist.

from vscode-livepreview.

I can make this a feature for the backlog to support localhost for launching, but I cannot guarantee that I can get to it soon. I can see the setting enabling launching localhost if livePreview.hostIP is set to 127.0.0.1

from vscode-livepreview.

Oh, no need for guarantees from me! :-) I appreciate just seeing it added to the backlog - thank you so much for that, and for all you've done to make this great extension!

from vscode-livepreview.