Rank: Advanced Member
Groups: Member
Joined: 2/11/2015
Posts: 122
|
Starting in Version 18.2.74 and continuing into the most recent versions.
The Custom Protocol Scheme behavior has changed, rendering some usages unavailable, however this isn't indicated in the documentation or in Change logs. I suspect this is a bug.
When a Webpage contains a Custom protocol scheme, such as "App://5349/" the value is translated into an IP Address and the ResourceHandler receives a value of "App://0.0.20.229/" instead.
I am providing a test project which should ease troubleshooting and displays the broken functionality.
the test is self contained so no hosting of pages should be necessary.
the project is setup with nuget to load 18.2.74 however any version after that can be used as well to reproduce the problem.
the EO.WebBrowser.Runtime.AddLicense call is in App.xaml.cs file and needs to be filled.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
This issue is caused by code changes in 18.2.74 that would automatically treat any custom protocol scheme as "standard" Url. We have reverted that code changes in build 19.0.83 so now it should revert to old behavior.
Thanks!
|