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
Backstory
I have an Ionic / Angular application which I host inside a .net WPF application, and use Webview2 to render the UI. We have a lot of users, who run demos using a local server. I had a user who reported the application would just not connect to his localhost. The ajax call returned no useful information, but from the dev tools I would see it being blocked.
One suggestion was to change
AppWebView.Source = new Uri("http://app/index.html")
to use https
AppWebView.Source = new Uri("https://app/index.html")
This fixed localhost, but then the QA team could no longer connect to their http only test VMS, i.e. non localhost (mixed content error). The the app is reported as broken
So the Webview2 ajax is useless to me, I had to forward all calls to use the hosting applications .net httpClient
So, is the above issue about fixing this, so we can use either http / or https, whatever we choose to use on either localhost and or remote servers? Sure everyone should use https, but it is just not the case in the real world (with test servers behind firewalls etc). I really could not tell which way it is going, fixing this, or causing this? We should be able to decide which we allow?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi just looking at the issue MicrosoftEdge/WebView2Announcements#126
Backstory
I have an Ionic / Angular application which I host inside a .net WPF application, and use Webview2 to render the UI. We have a lot of users, who run demos using a local server. I had a user who reported the application would just not connect to his localhost. The ajax call returned no useful information, but from the dev tools I would see it being blocked.
One suggestion was to change
to use https
This fixed localhost, but then the QA team could no longer connect to their http only test VMS, i.e. non localhost (mixed content error). The the app is reported as broken
So the Webview2 ajax is useless to me, I had to forward all calls to use the hosting applications .net httpClient
So, is the above issue about fixing this, so we can use either http / or https, whatever we choose to use on either localhost and or remote servers? Sure everyone should use https, but it is just not the case in the real world (with test servers behind firewalls etc). I really could not tell which way it is going, fixing this, or causing this? We should be able to decide which we allow?
Beta Was this translation helpful? Give feedback.
All reactions