8000 [BUG] GM_xmlhttpRequest does not support noCache · Issue #2168 · violentmonkey/violentmonkey · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BUG] GM_xmlhttpRequest does not support noCache #2168

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.

Sign up for GitHub

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

Jump to bottom
Open
superkeyor opened this issue Aug 19, 2024 · 2 comments
Open

[BUG] GM_xmlhttpRequest does not support noCache #2168

superkeyor opened this issue Aug 19, 2024 · 2 comments
Labels
enhancement interoperability interoperability of userscript engines, a difference in behavior needs investigation

Comments

@superkeyor
Copy link

Problem: GM_xmlhttpRequest does not support noCache

Expected result: if it supports noCache parameter (as mentioned at Tampermonkey/tampermonkey#962), it should allow to force retrieval of resources from Internet

Environment:

  • OS: Windows
  • Browser: Firefox 129
  • Violentmonkey Version: 2.20.0
@superkeyor superkeyor added the bug label Aug 19, 2024
@tophf
Copy link
Member
tophf commented Aug 19, 2024

Can't you use the classic method by setting the Cache-Control header?

@tophf tophf added the interoperability interoperability of userscript engines, a difference in behavior label Aug 27, 2024
@tophf
Copy link
Member
tophf commented Sep 1, 2024

Tampermonkey's solution don't seem sensible anyway. I'd simply implement cache option the way it's done in fetch.

@borkfomb borkfomb mentioned this issue Mar 10, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement interoperability interoperability of userscript engines, a difference in behavior needs investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tophf @superkeyor
0