ajax is built into webview. the only way to stop it would be to turn off javascript. or to turn off
internet connection.
who wrote the webview page that contains the ajax calls? why did he do that if he doesn't
want to allow ajax?
intercepting outgoing calls with webviewclient (ie, UltimateWebView2 or similar) might be
an option. eg, any calls not local or not going to a specific external server would be
intercepted and a message returned to caller indicating that such calls are not allowed.
i still don't understand how users are able to make their own ajax calls with the webview page
unless the page is specifically enabling it. that makes it difficult to stop them from doing what
they want.
in any case, a webviewclient handles a webview's heavy jobs behind the scenes. it
checks to see it it's supposed to intercept loading the request page. if it has been given no
reasons to intercept the loading, it passes the loading request on to its next task. otherwise,
it loads a custom page and passes it back to the caller instead of the requested url.
i don't know how ultimatewebview2 does that, but that's how intercept works. basically you
need to define the conditions for interception and the custom message.to be loaded.
(by the way, the author has self-deprecated ultimatewebview2 in favor of his webkitlibrary,
so you might need to look at that in any case).