Re: Apache EBCDIC to ASCII issue

Bob,

If you have CGIConvMode in your configuration, take it out. I vaguely
recall this being a problem for everyone who had it specified over at
Ignite/400.org when Apache first came out.

Also, if you happened to run the migration wizard/configuration mangler,
be prepared to have some fun with the crap it generates. I tried it on a
bunch of different server configurations and the only ones that even
worked were trivial (trivial to the point where just running the new
server wizard got you 95% of the functionality). In the end, I ran the
new server wizard for each of the instances I migrated and built them
out by hand. Besides actually working, the hand built ones also
performed better.

Matt 

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Bob Cozzi
Sent: Wednesday, January 25, 2006 1:29 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: [WEB400] Apache EBCDIC to ASCII issue

If I write directly from a SSI (CGI) program to QtmhWrStout, the server
seems to avoid doing the EBCDIC to ASCII conversion on the generated
HTML.

For example, I have a SSI that writes an HTML comment to the page with
the
number of visits to that particular page from your IP address.

On the old CERN server, there was no issue. Moving to Apache on V5R3,
this
particular SSI which writes to stdout using QtmhWrStout directly seems
to be
avoiding converting the data I'm sending to the browser. That is, it is
sending EBCDIC instead of ASCII. Hence I get a bunch of crap in the
browser.

Yet, if I use CGILIB (my version of a CGIDEV2-style library) and send a
huge
chunk of HTML (like my weekly surveys) everything is output correctly.
Ironically those interfaces also use QtmhWrStout.

I actually tested this by going into the visits counter program and
converting the data to CCSID(819) and then writing it via QtmhWrStout.
It
worked perfectly.

Yet no such conversion is performed in CGILIB as it lets the server
handle
conversions automagically, and there is never a problem.

I do see conflicting things in the midrange-l archives and on the
IBM.com
website with respect to CGIConvMode  %%EBCDIC/EBCDIC%% vs
%%MIXED/MIXED%%.

But I thought that was only used for encoding URL strings read by CGI
programs, not for writing data to the stdout.

Anyone else run into this kind of issue?

 

-Bob Cozzi

www.RPGxTools.com

RPG xTools - Enjoy programming again.