Re: [Q] Content length in MIME headers always right?
> I have a question regarding content length. Sometimes when
> I just fetch the header of a document I get a content length
> of -1 (i.e. unset), but if I get the entire document I get
> the correct content length. Can it be that the server creates
> different headers depending on whether you also ask for the
> document? Does this mean that the only way to get the content
> length with absolute certainty is to request the whole document?
There's a bug in NCSA HTTPd 1.5 and 1.5.1 where CGI script output
always shows a content length of -1. Could this be your problem?
73 de ke9tv/2, Kevin KENNY GE Corporate Research & Development
firstname.lastname@example.org P. O. Box 8, Room KWC273
Schenectady, New York 12301-0008 USA