You are correct.
I see it now:
3:56pm imp:[~] : %;
telnet www.HOST.upenn.edu 8080
Connected to XXX.XXX.UPENN.EDU (XXX.91.72.121).
Escape character is '^]'.
GET /pn21/secnet/section_text HTTP/1.0
HTTP/1.0 200 OK
Server: Zope/Zope 2.1.6 (source release, python 1.5.2, linux2) ZServer/1.1b1
Date: Thu, 08 Jun 2000 19:56:24 GMT
Why does Server: return linux2? This is an Compaq Alpha running Tru64!?!
On Thu, Jun 08, 2000 at 07:33:47PM +0200, Martijn Pieters wrote:
> On Thu, Jun 08, 2000 at 11:51:03AM -0400, Andrew Diller wrote:
> > It was just brought to my attention that Zope (using Zserver) is sending the wrong
> > type of all its pages.
> > Here is the header from zope: (some lines have been cut)
> > ------------------
> > HTTP/1.0 200 OK
> > Server: Zope/Zope 2.1.6 (source release, python 1.5.2, linux2) ZServer/1.1b1
> > Date: Thu, 08 Jun 2000 15:45:23 GMT
> > Ms-Author-Via: DAV
> > Content-Type: application/octet-stream
> > Last-Modified: Thu, 8 Jun 2000 15:45:07 GMT
> > Here is one from apache:
> > -------------------------
> > HTTP/1.1 400 Bad Request
> > Date: Thu, 08 Jun 2000 15:29:59 GMT
> > Server: Apache/1.3.6 (Unix)
> > Content-Type: text/html
> > I want Zope to be sending text/html, as some browsers want to download the page
> > than view it.
> You probably did a 'HEAD' request, at which point Zope doesn't render the
> page, but rather only acknowledges it's existence by returning above (bogus)
> If you do a 'GET' on your Zope resource, it _will_ be called, at which point
> Zope can determine what content type to send. Zope will guess the content type
> for you, usually this is text/html, but you can use the How-To you mentioned
> to tell Zope otherwise.
Zope maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -