--On Wednesday, February 27, 2008 23:57:48 +0100 Mel <[EMAIL PROTECTED]> 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/
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd";>
<HTML>
<HEAD>
       <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
       <TITLE>401 Unauthorized</TITLE>
       <LINK REL="STYLESHEET" TYPE="text/css" HREF="/cups.css">
</HEAD>
<BODY>
<H1>401 Unauthorized</H1>
<P>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.</P>
</BODY>
</HTML>

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 ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to