Hey! Did anything change regarding the
Hey! Did anything change regarding the MIME type?

7 Replies
Unknown User•10mo ago
Message Not Public
Sign In & Join Server To View
Seems, to be resolved now, without our intertervention
@Zino (Expatfile.tax) without seeing the network requests tab and based on your screenshot, I'd say the
s.js
request responded with 403 Forbidden and contained a user oriented message response with content-type text/html to show the error message. Then the 2nd error is because the browser did not want to interpret that 403 Forbidden response as a script because your root html file was served with a X-Content-Type-Options: nosniff
header telling the browser to be strict about content types.
So basically the real question is why would /s.js
ever respond with 403 forbidden? Does CloudFlare ever use this status code when throttling "malicious visitors" or scrapers? Perhaps your IP was making a few too many requests per minute while you were developing? Maybe a cloudflare rule was disallowing certain geographies or some other cloudflare level firewalling? I don't know the answer - but I think my understanding above will be correct around understanding the error. And I'm of course curious to know what the mechanism was that resulted in this!We noticed Cloudfare WAF is marking Zaraz calls with WAF Attack Score Class: Attack, @yo'av - we dont espect it to be marked as attack, anything changed here?
CC: @BensTechLab

Unknown User•10mo ago
Message Not Public
Sign In & Join Server To View
@yo'av - Any update on this?
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View