From owner-freebsd-questions@FreeBSD.ORG Wed Feb 27 23:19:19 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C464D1066415 for ; Wed, 27 Feb 2008 23:19:19 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id A21E18FC21 for ; Wed, 27 Feb 2008 23:19:19 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id F345065500 for ; Wed, 27 Feb 2008 17:19:18 -0600 (CST) Date: Wed, 27 Feb 2008 17:19:18 -0600 From: Paul Schmehl To: freebsd-questions@freebsd.org Message-ID: <1178DAFC04C10DF9E420A992@utd65257.utdallas.edu> In-Reply-To: <200802272357.50639.fbsd.questions@rachie.is-a-geek.net> References: <200802272357.50639.fbsd.questions@rachie.is-a-geek.net> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Cups not working X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 23:19:19 -0000 --On Wednesday, February 27, 2008 23:57:48 +0100 Mel wrote: > On Wednesday 27 February 2008 23:02:31 Paul Schmehl wrote: >> When I got to http://localhost:631/ I see the text (source) of the webpage >> rather than the page. (Cupsd is running.) I see this in >> /var/log/cups/access_log: >> localhost - - [27/Feb/2008:15:58:21 -0600] "GET / HTTP/1.1" 304 0 - - >> localhost - - [27/Feb/2008:15:58:45 -0600] "GET / HTTP/1.1" 304 0 - - >> localhost - - [27/Feb/2008:15:59:08 -0600] "GET / HTTP/1.1" 304 0 - - >> >> What am I missing? > > You're missing the first request. 304 means it should be in your browser > cache. > Either way, if you're seeing the source, it most likely means the webserver > sends text/plain as mime-type. > > curl -s -o /dev/null --dump-header /dev/stdout http://localhost:631/ > > should shed some light on it. Thanks. That does shed some light on it. # curl -s -o /dev/null -dump-header /dev/stdout http://localhost:631/ 401 Unauthorized

401 Unauthorized

Enter your username and password or the root username and password to access this page. If you are using Kerberos authentication, make sure you have a valid Kerberos ticket.

So I'm not being prompted for a login. If I go to http://localhost:631?, I can see the home page, but I can't get to anything because I'm not logged in. Since I'm never prompted for a login, it's a catch-22. Researching....... -- Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/