-
Notifications
You must be signed in to change notification settings - Fork 0
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
VS Code Launch inside WebView #8
Comments
Looks similar to #6 |
Yea it looks like that. Triple checked all of the bullets and of course it works in the external browser. Server Manager entry indeed defines a non-empty username. Also tried setting the httpProxy to not be strict as the letsencrypt cert chain has gotten a bit odd lately. It's like IIS w/ ISC Web Gateway doesn't properly ferry the OPTIONS call back through. I was tinkering with a React app that calls REST APIs in IRIS (though with apache) and I had to basically force apache to handle the OPTIONS/CORS response and then had success past that point. I'm not 100% on how to do that with IIS but I'll see if I can figure it out. |
Relevant ISC documentation link The IMPORTANT call out at the bottom of the section linked above seems pertinent and related to the callouts you made, so that makes sense but does better explain the reasoning. Of particular note, it explains why the 404 is returned for an OPTIONS call if privileges aren't addressed. Going to dig into that a bit and see if I can figure out what's happening. Will reply back. |
@CraigRegester I am doing some housekeeping. Are you still using this extension? |
Thanks for checking John - Not using this at the moment so all good here. Do what you need to do re housekeeping. :) |
Hey John! The extension is working great when accessed externally holding down the alt-key but I can't seem to get it to work launching inside webview.
Attached a screenshot from ISC Web Gateway trace showing what gets logged during the launch inside VS Code. I'm struggling to understand why it is returning a 404. I have it proxied through IIS 10 for SSL, Cert is trusted, and CSPms is set w/ * so proxying everything.
IIS logs show much of the same. Do we need to explicitly enable CORS in IIS to permit the preflight checks? Curious what your web.config looks like.
Using latest GA version of Server Manager.
The text was updated successfully, but these errors were encountered: