Sh... the damn xml is not coming out. Let's try again. This time I replaced the <> with []
>" [?xml version='1.0'?]
>" [clients]
>" [client]
>" [nom]"R" STORAGE LTD[/nom]
>" [code]403-849-63[/code]
>" [/client]
>" [client]
>" [nom]# TEXAS INSTR. (SERVICES)[/nom]
>" [code]000967[/code]
>" [/client]
>" [client]
>" [nom]#1 PET CENTRE[/nom]
>" [code]416-942-36[/code]
>" [/client]
>" [client]
>" [nom]#1 PET CENTRES[/nom]
>" [code]905-454-26[/code]
>" [/client]
>" [/clients]

>Sorry, it didn't came out correctly:
>I am creating xml output from a cgi (little exe pgm that reads standard input and write standard output) program (using IIS). It produces the following error:
>The specified CGI application misbehaved by not returning a complete
>set of HTTP headers. The headers it did return are: ...
>
>If I read the same http file just with the II5, without going trought cgi,, no problem.
>the output looks like this:
>
>"
>"
>"
>" "R" STORAGE LTD
>" 403-849-63
>"
>"
>" # TEXAS INSTR. (SERVICES)
>" 000967
>"
>"
>" #1 PET CENTRE
>" 416-942-36
>"
>"
>" #1 PET CENTRES
>" 905-454-26
>"
>"
>"
>From http://support.microsoft.com/support/kb/articles/Q150/8/35.asp?LN=EN-US&SD=gn&FR=0, it seems that the first line must be strictly one of the following:
> Content-type:
> Location:
> STATUS
>
>Any suggestion for a workaround ?
>
>
>Thanks
>Eric
>>I am creating xml output from a cgi (little exe pgm that reads standard input and write standard output) program (using IIS). It produces the following error:
>>The specified CGI application misbehaved by not returning a complete
>>set of HTTP headers. The headers it did return are: ...
>>
>>If I read the same http file just with the II5, without going trought cgi,, no problem.
>>the output looks like this:
>>
>>
>>
>>
>> "R" STORAGE LTD
>> 403-849-63
>>
>>
>> # TEXAS INSTR. (SERVICES)
>> 000967
>>
>>
>> #1 PET CENTRE
>> 416-942-36
>>
>>
>> #1 PET CENTRES
>> 905-454-26
>>
>>
>>
>>From http://support.microsoft.com/support/kb/articles/Q150/8/35.asp?LN=EN-US&SD=gn&FR=0, it seems that the first line must be strictly one of the following:
>> Content-type:
>> Location:
>> STATUS
>>
>>Any suggestion for a workaround ?
>>
>>
>>Thanks
>>Eric