We're updating the issue view to help you get more done. 

Content-Type is not set for JavaScript files

Steps to reproduce

Steps to reproduce:
1. Start Opencast
2. curl -I http://<opencast>/engage/ui/js/lib/require.js
HTTP/2 200
server: nginx
date: Wed, 24 Jan 2018 15:13:28 GMT
content-length: 15924
set-cookie: JSESSIONID=1ung7btes94oz1ffabfg6zwsii;Path=/
expires: Thu, 01 Jan 1970 00:00:00 GMT
etag: 2444ded40a4aa435d44738b0e285c183
strict-transport-security: max-age=63072000; includeSubdomains
x-content-type-options: nosniff
x-xss-protection: 1; mode=block

Actual Results:
The content type header is not set. Since our reverse proxy sets `x-content-type-options: nosniff` the browser rejects to execute the JavaScript code.

Expected Results:
The content type is set to application/javascript

Status

Assignee

Matthias Neugebauer

Reporter

Matthias Neugebauer

Severity

Non Functioning

Tags (folksonomy)

None

Components

Fix versions

Affects versions

4.0

Priority

Minor