Re: tlug: HTTP headers q

[Darren Cook <darren@example.com>]

>When I "fixed" things so that Content-type: and the Pragma: both output
>always, and added the empty line, I got what looks like *Apache's*
>Content-type: header (text/plain) as part of the text of the document when

This sounds like Apache couldn't see your Content-type header. Is it
correctly formatted? What happens if you get rid of the charset?


>do is fix the Content-type: header in the CGI and persuade Apache to just
>trust me and pass my headers through to the client verbatim.  I think that

Prefixing the script name with "nph-" (non-parsed headers) does exactly that.

This seems to be the only FAQ entry on it:
  ...apache/manual/misc/FAQ.html#nph-scripts


>the FastCGI interface ....

Do you actually have a performance problem? And if so can that be blamed on
the cost of cgi script startup?

Darren

--------------------------------------------------------------------
Next Nomikai Meeting: February 18 (Fri) 19:00 Tengu TokyoEkiMae
Next Technical Meeting:  March 11 (Sat) 13:00 Temple University Japan
* Topic: TBD
--------------------------------------------------------------------
more info: http://www.tlug.gr.jp        Sponsor: Global Online Japan