Thanks for the input. I am using the QtmhRdStin api to parse the
query_string. Yes, the conversion mode was a typo. My config says
%%EBCDIC/MIXED%%.

Thanks


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of web400@xxxxxxxxxxxxxxxx
Sent: Wednesday, January 03, 2007 1:40 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Cgi Conversion

Hello,

I have been running a cgi (rpg) program for years the takes 2 
parameters and generate a page. The second parameter could blanks in 
it and I handled it using the escape sequence %20 in the generated 
url. It looks like /?00220+A%20T%20. We recently went to V5R4 and now 
my escape sequence is being ignored (%20 not being converted to blank).

How are you parsing the QUERY_STRING?   Is this a routine that you wrote? 
Or are you calling an API of some kind?  Or CGIDEV2?  Or....?

Neither Apache nor the original server will convert %xx to a character for
you.  It's up to your application, or an API that you call, such as the ones
I listed above, to convert %20 to a blank, or %xx to the appropriate
character.


My apache instance config says cgiConvMode %%EBCIDIC%%/%%MIXED%%. This 
application worked fine on V5R3.

Hmmm... your CgiConvMode has some typos in it.  Are they typos in your
actual configuration file, or just in the e-mail you sent to this list?

It should look like this:

    CgiConvMode %%EBCDIC/MIXED%%

Yours, however, has an extra "I" in the word "EBCDIC", and has added extra
percent symbols to the middle of the string. So I'm wondering if that error
is actually in your config file, or if it's just a typo in your e-mail.  If
it's actually like that in the config file, that might be part of the
problem.


This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].