Help understanding WV2 host name resolution vs. .NET HttpWebRequest #4550
Unanswered
ShaunLoganOracle
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The scenario is an Excel VSTO add-in We are using WebView2 for allowing users to establish a session with a web application (ie. log in). Then the add-in uses information captured from WV2 to make additional requests to the web app via .NET
HttpWebRequest
. This has been working well for many customers.However some customers are reporting that although the WV2 login sequence (accessing host eg. abc.mycompany.com) succeeds, then the subsequent .NET request to the same host fails with:
WebException - The remote name could not be resolved: 'abc.mycompany.com' status: NameResolutionFailure
What configuration controls WV2's name resolution and how can I get HttpWebRequest to respect that same configuration?
Beta Was this translation helpful? Give feedback.
All reactions