> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 25, 2002 10:26 AM > To: Kyle Babich; [EMAIL PROTECTED] > Subject: Re: Displaying Problems > > > Kyle, > Well, I'd start by printing an actual content type > instead of depending on CGI.pm for that: > --------------------------------------- > print "content-type: text/html\n\n";
Except that that's not RFC2616-compliant, while CGI.pm's output is. Most browsers will accept this, but you still shouldn't generate it. > ... > Then I would HIGHLY recommend that you not depend on > CGI.pm so heavily. I would suggest you > print out your own html, then you can see exactly what it is > displaying and know what to change. I fail to see how writing code with errors is somehow CGI.pm's fault. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
