> Brian Lloyd wrote:
> > What if we change this to:
> >
> > if a 'content_type' attribute exists, it is used
> >
> > else if the object's id seems to have a file extension
> > (. in the id), try to use guess_content_type
> >
> > > else if there is a 'default_content_type' attribu
On Thu, 8 Jun 2000, Andrew Diller wrote:
> Server: Zope/Zope 2.1.6 (source release, python 1.5.2, linux2) ZServer/1.1b1
>
> Why does Server: return linux2? This is an Compaq Alpha running Tru64!?!
No. That's what you are told it is.
In fact it's an i386 under GNU/Linux ;-))
bye,
Jerome ALET -
Brian Lloyd wrote:
> What if we change this to:
>
> if a 'content_type' attribute exists, it is used
>
> else if the object's id seems to have a file extension
> (. in the id), try to use guess_content_type
>
> > else if there is a 'default_content_type' attribute, use that
It w
> -Original Message-
> From: Dan L. Pierson [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 08, 2000 3:47 PM
> To: Brian Lloyd
> Cc: 'Chris Withers'; Martijn Pieters; Andrew Diller; [EMAIL PROTECTED]
> Subject: RE: [Zope] Wrong mime type sent by Zope on
Brian Lloyd writes:
> What if we change this to:
>
> if a 'content_type' attribute exists, it is used
>
> else if the object's id seems to have a file extension
> (. in the id), try to use guess_content_type
>
> > else if there is a 'default_content_type' attribute, use t
> > But what if there are side effects to calling the document?
> What should
> > happen? I don't want a counter to go up or anything just
> because a HEAD was
> > called on the object.
> >
> > This is not as black-and-white and simple an issue.
>
> The web is an imperfect medium, but returnin
You are correct.
I see it now:
3:56pm imp:[~] : %;
telnet www.HOST.upenn.edu 8080
Trying XXX.91.72.121...
Connected to XXX.XXX.UPENN.EDU (XXX.91.72.121).
Escape character is '^]'.
GET /pn21/secnet/section_text HTTP/1.0
HTTP/1.0 20
Martijn Pieters wrote:
> But what if there are side effects to calling the document? What should
> happen? I don't want a counter to go up or anything just because a HEAD was
> called on the object.
>
> This is not as black-and-white and simple an issue.
The web is an imperfect medium, but retur
On Thu, Jun 08, 2000 at 06:59:29PM +0100, Chris Withers wrote:
> Martijn Pieters wrote:
> > 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)
> > response.
>
> That's not very search engine fr
Martijn Pieters wrote:
> 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)
> response.
That's not very search engine friendly :(
The head should return the same type as the real document otherwi
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
>MIME
> type of all its pages.
>
> Here is the header from zope: (some lines have been cut)
> --
>
> HTTP/1.0 200 OK
> Server: Zope
11 matches
Mail list logo
