Report Blog Entry
My layout was several hundred lines long and would only work if I used a css import statement to link to an external sheet that I keep on Neocities. At some point in the past few weeks, they made a change with their proxy that forces all proxied text content to get sent to the browser as html text. Since this is supposed to be loaded as css, web browsers reject this for security reasons (otherwise people could inject malicious content into the page).
This issue is caused solely by the SpaceHey proxy returning the incorrect mimetype for external css sheets. I attempted to contact support but am getting nothing but silence.
It is extremely disappointing that the literal months of effort that went into my profile and blog layouts have been wiped out.
If you would like to find me elsewhere, I am on mastodon @engiqueering@gaygeek.social where I mostly post pictures of my cats
Comments
Displaying 1 of 1 comments ( View all | Add Comment )
An
Hi! Haven't changed anything with the proxy lately, so that's super weird! Do you have any deatils - URLs, etc so I can look into it?
I sent an email with the subject "CSS import statements broken" to support@spacehey.com from dev@engiqueering.com a little while ago that has screenshots, but the issue is that the proxy is returning my CSS imports with the content-type header "text/html; charset=UTF-8" when it should be "text/css".
This is resulting in the following console error:
The resource from “https://external-media.spacehey.net/css/sQJA7rjIWdDgQYd-STNNs90uiIBC8XOUCG_10CYOSpes=/https://engiqueering.com/spacehey/style_new.css” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
In other words, the resource failed to import because the MIME type in the header is wrong.
I did a test to make sure that NeoCities hadn't changed the header type on their end but when I do a GET request on the original source I get "text/css" back as the content-type, so it's definitely an issue with the proxy.
by EngiQu33ring; ; Report
Hey, looks like the issue is resolved now. If you looked into it and made some changes, I appreciate it; if it fixed itself then I'll just chalk this up to gnomes in the wires taking a cheap shot at me again.
Either way, everything works again and I am excited to finish a profile framework I started on years ago and have been waiting for a CSS selector to finally hit the major browsers so I could finish it!
by EngiQu33ring; ; Report