Hey guys,

I have been searching the forms for Cobalt errors similar to mine upon install, and it appears that most (if not all) of the "Bad Header" errors people are getting are coming from an install of Links 2. I am wondering if those fixes posted for Links 2 could be used for Links SQL2 as well.

Everything seems to install fine, but I can't use the import feature (among a few others - but the import is most important at this time).

Here is the error from my log:
[Sun Aug 19 02:34:09 2001] [error] [client 208.44.118.137] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/cgiwrap/cgiwrap

Thank you,

Chad J

Actually, the nph-* files do not appear to have any lines that print html headers, so if anyone can help me get rid of this error, I would appreciate it.

Hi,

In the SQL Link version there's an option in
setup > Misc Options
where you can select not to use Parsed Headers.
Setting nph_headers = no will probably solve the problem.

Hope this helps

Rudi Tielemans

Awesome Rudi!

Looks like it is going to work.

Thanks for your reply!