javascript and css files are encoded in nginx

somedude

4/20/24, 11:43 AM

I have a reverse proxy that returns only the javascript and css in some encoding. I do not know if it is encoded or just not decompressed.

This is wat the server returns: ��^style.css��;ks�:��;S��d�y�WMjIB2�3I

this is what I expect: *{margin:0;padding:0}

My html loads in just fine it's only the css and js files. I already tried turning on/off gzip and brotli. I also tried proxy_set_header Accept '*/*'; but that also did not help.

I can see in the developer tools that the response headers are: Content-encoding: gzip and Content-type: text/css; charset=utf-8. and the request header accept: text/css,*/*;q=0.1

I do see this application/x-javascript; charset=utf-8 as Content-type for the javascripts.

when I directly access the server all files are served correclty. I don't know what the problem is or where too look at.

146

0 + 0

http

nginx

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: javascript and css files are encoded in nginx

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.