David Helstroom wrote:
Hi John,
Just a quick thought - a thought quite possibly well and truly off
track - could it be related to mime-types? Perhaps the CUPS web server
has a problem recognising the HTML mime-type and thus is not sending
them in the appropriate format (and with appropriate HTTP headers)?
I think you've got it. I did a wget -S http://localhost:631 on both the
affected and
unaffected machines. On the affected machine, wget reported
Content-Type: text/plain; charset=utf-8
On an unaffected machine, wget reports
Content-Type: text/html; charset=utf-8
So, now we know that cupsd is definitely confused on the affected
machine. How to get
it unconfused? I've tried emerge -C cups, then emerge cups, but that
doesn't fix the
problem.
John
--
[email protected] mailing list
