From: John Blinka <jblinka@neo.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cups is broken
Date: Sun, 26 Feb 2006 10:17:42 -0500 [thread overview]
Message-ID: <4401C696.5060705@neo.rr.com> (raw)
In-Reply-To: <4401C1D5.9080401@student.usyd.edu.au>
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
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-26 15:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 19:25 [gentoo-user] cups is broken John Blinka
2006-02-25 19:51 ` Ernie Schroder
2006-02-25 21:22 ` John Blinka
2006-02-25 22:13 ` Ernie Schroder
2006-02-26 0:12 ` John Blinka
2006-02-26 3:28 ` Ernie Schroder
2006-02-26 12:20 ` John Blinka
2006-02-26 14:18 ` Ernie Schroder
2006-02-26 14:40 ` John Blinka
2006-02-26 15:26 ` Ernie Schroder
2006-02-26 15:34 ` John Blinka
2006-02-25 23:16 ` Jerry McBride
2006-02-26 14:57 ` David Helstroom
2006-02-26 15:17 ` John Blinka [this message]
2006-02-26 15:38 ` Uwe Thiem
2006-02-26 16:36 ` John Blinka
2006-02-26 18:10 ` Uwe Thiem
2006-02-26 19:26 ` John Blinka
2006-02-26 20:43 ` Boyd Stephen Smith Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4401C696.5060705@neo.rr.com \
--to=jblinka@neo.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox