and even if it was exposed it conflicts with current behavior i.e. command line parameter when you create that external sub process)Īlas in QT you can change QCoreApplication::arguments() only once right before you create the app - QCoreApplication app(argc, argv) īut this is not exposed (per Web Page/View but only at app level) Chromium in C# with CefGlue there is a way to set proxy per tab (yes it is static - you cannot change it later but at least you have an option to change/set/provide it through -proxy-server=. NB! Proxy per URL is not the same as proxy per tab There are many plugins that apply different proxies per URL e.g. The only alternative is proxy for URL - if that is OK with you. what will happen for page with 10 iframes loading different URLs and applicationProxy changes after first 5 iframes loaded - will remaining 5 iframes use old or new applicationProxy? I did a quick test with demobrowser - apparently with every request the proxy changes to the current QNetworkProxy::applicationProxy alas we have no exposure to command line per external QtWebEngienProcess.exe or QtWebEngienProcessd.exe and then we have to disable current applicationProxy to have a proxy per tab/page if you set proxies both by QNetworkProxy::applicationProxy and by QCoreApplication::arguments() which one will be used? yet documentation is so scarce I'm having hard time finding information about e.g. sandboxing) to pass the proxy at creation time using command line parameters (yes per tab/page! btw: you can see external processes in task manager - just open demobrowser with few tabs).
The proper way in Blink is (because Blink uses external 'browser' process per page/tab a.k.a. It is by design (in Blink - Chromium web engine) - it is a real browser and (perhaps for security reasons) it acts like one i.e.
because we can change QNetworkProxy::applicationProxy at any time - Does WebEngine get feedback about those changes and how? they say "If QNetworkProxy::applicationProxy is set, it will also be used for Qt WebEngine." but what they don't say is HOW: is it read only once at (web page) creation time, checked periodically (at known times, at unknown times). When you use the string syntax: eg: serveStatic. Options that are passed to the serve-static middleware Run in proxy mode where files under /assets will be served // from either the. Run in proxy mode where files under /assets + /content will be served // from a local. Run in proxy mode where files under /assets will be served // from a local. Run in proxy mode with static files also served // from current directory +. Var bs = require( 'browser-sync').create() Browsersync will wrap your vhost with a proxy URL to view your site. Since version 1.2.1 // The key is the url to match // The value is which folder to serve (relative to your current working directory) The static file server is based on expressjs/serve-static, // so we inherit all of their options, like trying a default extension // when one isn't specified // Serve files from the app directory, with a specific index filename Server: true // Serve files from the app directory with directory listing Server: "app" // Serve files from the current directory
0 kommentar(er)
