Fixing content types in status router

As it turns out, expressjs doesn't detect the right mimetype and it
seems like I didn't bother to test this enough. So lets fix it for the
next release.

Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
This commit is contained in:
Sheogorath 2018-07-03 20:36:40 +02:00
parent 4e38d1836e
commit d76ea5440a
No known key found for this signature in database
GPG key ID: 1F05CC3635CDDFFD

View file

@ -17,7 +17,8 @@ statusRouter.get('/status', function (req, res, next) {
realtime.getStatus(function (data) { realtime.getStatus(function (data) {
res.set({ res.set({
'Cache-Control': 'private', // only cache by client 'Cache-Control': 'private', // only cache by client
'X-Robots-Tag': 'noindex, nofollow' // prevent crawling 'X-Robots-Tag': 'noindex, nofollow', // prevent crawling
'Content-Type': 'application/json'
}) })
res.send(data) res.send(data)
}) })
@ -101,7 +102,8 @@ statusRouter.get('/config', function (req, res) {
} }
res.set({ res.set({
'Cache-Control': 'private', // only cache by client 'Cache-Control': 'private', // only cache by client
'X-Robots-Tag': 'noindex, nofollow' // prevent crawling 'X-Robots-Tag': 'noindex, nofollow', // prevent crawling
'Content-Type': 'application/javascript'
}) })
res.render(config.constantsPath, data) res.render(config.constantsPath, data)
}) })