RE: HTTP after V4R2 upgrade

I know. I managed to resist temptation and did call them back. 

>----------
>From:  Neil Palmer[SMTP:npalmer@NxTrend.com]
>Sent:  Tuesday, March 24, 1998 4:50 PM
>To:    'MIDRANGE-L@midrange.com'
>Subject:       RE: HTTP after V4R2 upgrade
>
>Albert,
>
>You may be sorely tempted, but think of all the other poor sods who may
>run into the same problem and wait forever for a solution if they don't
>know about Midrange-L, and IBM doesn't have the solution in their
>database.    :-(
>
>
>
>Neil Palmer                                AS/400~~~~~      
>NxTrend Technology - Canada   ____________          ___  ~     
>Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
>Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
>Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
>Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
>mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
>http://www.NxTrend.com
>
>> -----Original Message-----
>> From:        York, Albert [SMTP:albert.york@nissan-usa.com]
>> Sent:        Tuesday, March 24, 1998 4:08 PM
>> To:  'MIDRANGE-L@midrange.com'
>> Subject:     RE: HTTP after V4R2 upgrade
>> 
>> Thanks Darin. That worked like a charm (after I ended and restarted
>> the
>> HTTP server). I had previously called IBM and they are still
>> scratching
>> their heads. I'm tempted to not call them back and tell them the
>> solution.
>>  
>> 
>> >----------
>> >From:       Darin White[SMTP:darin@netserv.ouac.on.ca]
>> >Sent:       Tuesday, March 24, 1998 7:50 AM
>> >To:         MIDRANGE-L@midrange.com
>> >Subject:    HTTP after V4R2 upgrade
>> >
>> >Problem solved.
>> >
>> >Turns out we had old versions of QTMHCGI and QTMHIMAG in our CGIBIN 
>> >library (cgi executable directory) that were carried forward from the
>> 
>> >old OS.  After copying new versions into CGIBIN from QTCP everything 
>> >worked again.
>> >
>> >Darin
>> >
>> >------- Forwarded Message Follows -------
>> >From:          "Darin White" <darin@netserv.ouac.on.ca>
>> >Organization:  OUAC
>> >To:            MIDRANGE-L@midrange.com
>> >Date:          Tue, 24 Mar 1998 09:42:58 EDT
>> >Subject:       (Fwd) HTTP after V4R2 upgrade
>> >Reply-to:      MIDRANGE-L@midrange.com
>> >
>> >We're having the same problem as Albert.  CGI's were running on V3R2 
>> >and V4R1 but totally conked out on V4R2.  I thought it might be the 
>> >beta of V4R2 but an install of the production version of the OS 
>> >last week didn't help.  The only reason we're on 4.2 is to run 
>> >Net.Commerce, but I didn't expect this side-effect.
>> >
>> >I'm in an extended dialogue with IBM on this problem: sending them 
>> >configuration files, httpd traces, etc.  No solutions yet.  Anybody 
>> >have any ideas?
>> >
>> >Darin
>> >
>> >------- Forwarded Message Follows -------
>> >From:          "York, Albert" <albert.york@nissan-usa.com>
>> >To:            "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
>> >Subject:       HTTP after V4R2 upgrade
>> >Date:          Mon, 23 Mar 1998 16:19:41 -0800
>> >Reply-to:      MIDRANGE-L@midrange.com
>> >
>> >We recently upgraded to V4R2 and our CGI-BIN programs stopped
>> working.
>> >We keep getting the following error message in the browser: 'Error
>> 500
>> >Internal error: headers' .
>> >
>> >The programs worked fine before. What's different?
>> > 
>> >
>> >
>> >_____________________________________________________________________
>> _
>> >Darin White
>> >Software Developer
>> >Ontario Universities' Application Centre
>> >P.O. Box 1328, 650 Woodlawn Road West
>> >Guelph, Ontario  CANADA  (519) 823-1940 x255  darin@ouac.on.ca
>> >_____________________________________________________________________
>> _
>> 
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator: david@midrange.com
>+---
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---