Skip to content

Home

  • in diary
  • 1 min read

diary record

Cloud workflows are another level of a mess, not quite a news, is it? A peculiar case of my little struggle with chaos - devops does not have capacity to assign me the access to some db. And I have to deliver little code, involving the other code (not mine), involving that db. Yay, workaround - I do have an access to deployment pipeline, which spins up the container with the access to that db. So my journey is like a hangman game - assume, change code, deploy (10 minutes), check. Trying restart the app within that container relaunches the container. So, this is the way. And I have some time to write this grumpy post.

django app: Resource blocked due to MIME type mismatch

Running your Django app first time in production, you might bump into the issue of your browser blocking static resources (.css, .js) with a message "Resource blocked due to MIME type mismatch". I was googling a bit here and there, most results are providing a bit context demanding answers.

"Hint"

The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the MIME types advertised in the Content-Type headers should be followed and not be changed.

(The document provided by the link "explaining" the issue in the browser)

Dude, what do I do? Some answers on Stack Overflow recommend to turn of security features in your browser. Well, swiping the issue under the carpet does not make it go.