We found that if we serve kitto dashboard behind nginx, chrome or safari will download the dashboard, rather than serving it as an html page. The reason is "content-type" of response is not properly set by kitto.
Coverage remained the same at 88.636% when pulling 56b3155bd3a0eee35aa0e42cf9459b825bf48262 on leineu2016:master into e80c54b873ec6a444ae2f53e9975c0b1f8237159 on kittoframework:master.
Coverage remained the same at 88.636% when pulling 56b3155bd3a0eee35aa0e42cf9459b825bf48262 on leineu2016:master into e80c54b873ec6a444ae2f53e9975c0b1f8237159 on kittoframework:master.
Coverage remained the same at 88.636% when pulling 56b3155bd3a0eee35aa0e42cf9459b825bf48262 on leineu2016:master into e80c54b873ec6a444ae2f53e9975c0b1f8237159 on kittoframework:master.
Coverage remained the same at 88.636% when pulling cb6f9cf3904d19bbe16763f0b31c91c67dd94741 on leineu2016:master into e80c54b873ec6a444ae2f53e9975c0b1f8237159 on kittoframework:master.
We found that if we serve kitto dashboard behind nginx, chrome or safari will download the dashboard, rather than serving it as an html page. The reason is "content-type" of response is not properly set by kitto.