Native HTTP basic auth dialog suppression shifts to chromium-args in NW.js 0.48.0
0 reputation · 10 Mar 2020, 20:06 UTC
Native HTTP basic auth dialog suppression shifts to chromium-args in NW.js 0.48.0
An NW.js application calls a remote endpoint that returns 401 with a WWW-Authenticate header. Chromium displays its native basic-auth dialog, which neither fetch nor XMLHttpRequest can override. The project is upgrading from NW.js 0.47.x to 0.48.x or later, and the supported way to pass Chromium flags changed from a command-line argument to the package.json chromium-args field.
It is uncertain whether --disable-http-auth still works when passed only on the command line after 0.48.0, or whether it must appear exclusively under chromium-args in the manifest. It is also unclear whether omitting the field keeps the native dialog enabled across Windows, macOS, and Linux.
Does NW.js 0.48.0 and later ignore --disable-http-auth when supplied outside package.json? Should chromium-args replace the command-line flag entirely, or can both coexist? Is suppression behavior consistent across operating systems for the same NW.js version?
nodewebkit