When you open devtools, by default it will try to load source code maps for your JS and CSS.
Very simple for a system to detect the request for the map file.
If that's their vector turn off the autoloader and try from a clean IP.
Very simple for a system to detect the request for the map file.
If that's their vector turn off the autoloader and try from a clean IP.
Edit: You can redefine console.log to be a noop, but that's also detectable.
foo.toString = () => console.warn("called")
console.log(foo)
...and how to disable them from auto-loading.
I mean, okay, I can see how they definitely have a use. But to try and auto-fetch js and css maps just because I want to have a look at the DOM?
Why not wait until I actually try looking at js/css? Or even until I ask to see the source map?
Prefetching never feels right to me. Even though I know GET requests are supposed to be side-effect free and idempotent (and if they're not, that's a choice by the server devs and they'd better have covered all the edge cases where clients correctly act as if they are...), it has the architectural equivalent of a "code smell" to my nose.
Could yours be a Windows Group Policy from $WORK?
[0] https://x-c3ll.github.io/posts/javascript-antidebugging/
The source map requests was a more successful option. Also played around with "snap" resize but it was too agressive.
As for whatever the reason MailChimp would block your up is pretty ridiculous.