Ability to change baseurl
See original GitHub issueDescription
Hey guys,
This is related to https://github.com/dotnet/aspnetcore/issues/35077 and I’m having a similar problem. and yes, this is a blocker for many use cases many people posted.
I’m suggesting an alternative solution: ability to change the base URL and let users choose to traffic fall through when base URL interception is not hit.
Public API Changes
Need to expose and give the ability to change outside of framework somehow:
on a side note: this won’t make requests substantially faster because there’s will be no DNS resolution as long as we intercept.
and even if they do resolution will be cached so this will be premature optimization, don’t they?
Intended Use-Case
So similar to this issue (https://github.com/dotnet/aspnetcore/issues/35077)
example baseurl: contoso.com
- case 1
- app start
- app shows the initial page
- app trying to send ajax POST to contoso.com/some-api (not working, we need a server or fall through to browser request instead of injection)
- app continues to run
- case 2
- app start
- app shows the initial page
- user input, app trying to redirect to a dynamic page with the same domain which only available via the server
- server redirects the user back to the original page
This is important because users shouldn’t alter their entire architecture because MAUI is not supporting it.
Issue Analytics
- State:
- Created 10 months ago
- Reactions:1
- Comments:5 (1 by maintainers)

Top Related StackOverflow Question
One more use case: Since 0.0.0.0 is not considered as secure context by some old web views you get limited access to browser api via JS. Cordova allows changing is via hostname property in config.xml.
Example: iOS 14.5
It works on iOS 16.3 but we need to be backward compatible, iOS 14.X is still 6-14% of iOS market. So I’d make it configurable and default to 0.0.0.0. https://bugs.webkit.org/show_bug.cgi?id=220184
You can use WebRTC native libraries to get media devices but it doesn’t work on iOS because of bindings issue + it’s not fully hybrid approach (we have blazor wasm app as well). So @christallire the only workaround so far is:
@Bohdandn thanks for the workaround. I was about to try WebRTC too! it would save a ton of time.
One funny thing is that it renders clarity (from Microsoft) unusable too.