Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GM_xmlhttpRequest does not work anymore with required Windows Authentication #2157

Closed
msteinic opened this issue Aug 16, 2024 · 2 comments
Closed

Comments

@msteinic
Copy link

Expected Behavior

Website with required Windows Authentication ->
Windows Authentication needs to get passed via GM_xmlhttpRequest (as it worked in previous Tampermonkey Mv2, f.e. 5.1.1) to be able to get access to the requested file/website.

chrome_Mv2_direct_to_https_tpmLegacy_5 1 1

Actual Behavior

In Tampermonkey for Mv3 (f.e. v5.2.3 and latest beta 5.3.6207) the Windows Authentication apparently does not get passed to the page/file i try to access via GM_xmlhttpRequest.
Due to that im getting a 401 unauthorized when trying to access the page/file which requires the Windows Authentication.

chrome_Mv3_direct_to_https_tpmLatestBeta

Specifications

  • Chromium: 127.0.6533.120
  • TM: 5.3.6207
  • OS: Windows 11

Script

// ==UserScript==
// @name Script
// @match https://exampleWebsite.com/*
// @grant GM_xmlhttpRequest
// ==/UserScript==

GM_xmlhttpRequest({
method: "GET",
url: "https://example.com/json/jsonData.json",
responseType: "json",
onload: function (result) {
console.warn(result.status);
}
});

@derjanb derjanb added the bug label Aug 26, 2024
@derjanb derjanb added this to the 5.3 milestone Aug 26, 2024
@derjanb
Copy link
Member

derjanb commented Aug 28, 2024

Should be fixed at 5.3.6208 (crx|xpi in review)

Please download the crx file linked above and drag and drop it to the extensions page chrome://extensions (after you've enabled 'Developer Mode').

For a quick fix please export your settings and scripts as zip or (JSON) file at the "Utilities" tab and import it back at the fixed BETA version.

@msteinic
Copy link
Author

Tested it in several scripts. This new version fixed the bug.
Thank you very much.

@derjanb derjanb closed this as completed Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants