tags 931831 moreinfo thanks
On Thu 11 Jul 2019 at 05:30:32 +0000, Witold Baryluk wrote: > Package: cups > Version: 2.2.10-6 > Severity: important > > > $ curl -v http://localhost:631/ > ... > > GET / HTTP/1.1 > > Host: localhost:631 > > User-Agent: curl/7.64.0 > > Accept: */* > > > < HTTP/1.1 200 OK > < Connection: Keep-Alive > < Content-Language: en_US > < Content-Length: 2364 > < Content-Type: text/plain > < Date: Thu, 11 Jul 2019 05:27:25 GMT > < Keep-Alive: timeout=10 > < Last-Modified: Tue, 23 Apr 2019 06:33:01 GMT > < Accept-Encoding: gzip, deflate, identity > < Server: CUPS/2.2 IPP/2.1 > < X-Frame-Options: DENY > < Content-Security-Policy: frame-ancestors 'none' > < > <!DOCTYPE HTML> > <html> > <head> > <link rel="stylesheet" href="/cups.css" type="text/css"> > <link rel="shortcut icon" href="/apple-touch-icon.png" type="image/png"> > <meta charset="utf-8"> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> > <meta http-equiv="X-UA-Compatible" content="IE=9"> > <meta name="viewport" content="width=device-width"> > <title>Home - CUPS 2.2.10</title> > </head> > <body> > <div class="header"> > ... > > > Obviously this is not correct. > > CUPS should serve it as Content-Type: text/html > > Firefox and Chromium display the served data as raw text, making web > interface unusable. Thank you for both your reports, Witold. With cups 2.3.3op2-6 and 2.3.3op2-7 (the present unstable version) I get: brian@desktop:~$ curl -sSi http://localhost:631/ | grep ^Content-Type Content-Type: text/html; charset=utf-8 brian@desktop:~$ Please would you test with either of these versions. Regards, Brian.
