Closed pharrisee closed 6 years ago
Hmm, seems the browser is requesting with a accept-content-type header = 'text/plain' , which aah then uses (correctly) to send .
More investigation required on my part.
@pharrisee Okay, please let me know after your investigation then I will start analysis at my end. Is it a edge version?
I have just did a small update on static file content type detection on single binary mode. You could refresh aah s -r
to updates.
FYI, aah single binary does optional decompression (sends already gzipped bytes as-is from VFS) while delivering static files 😄
Any insights or test results would be helpful.
I have verified at my end. With previous update on edge, its doing fine.
Hi,
I'm getting a browser side error:
This seems to be related to this header being set:
Since that header is set to nosniff the mime-type of the static files should be set explicitly.
This is when starting the aah app in dev mode with
aah r
.