× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is strange behavior. You would expect it to always return in whatever the DefaultNetCCSID is, or whatever the DefaultFsCCSID is. It is strange that it would use the DefaultNetCCSID when it is 1208 and the DefaultFsCCSID when the DefaultNetCCSID is 819.

Sounds like a bug to me.

On 7/2/2015 9:40 AM, Henrik Rützou wrote:
Scott

I moved the program to a apache instance with defaultNetCCSID 819 at it
returns
EBCDIC

On Thu, Jul 2, 2015 at 4:32 PM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
wrote:

When you run this, it returns the URI in UTF-8? It has always returned
the URI in EBCDIC when I've done it.

On 7/2/2015 9:25 AM, Henrik Rützou wrote:

Scott

there is one thing in your presentation I have tested and is wondering
about ...

data = %str(getenv('QUERY_STRING)); // returns the parms section in EBCDIC

data = %str(getenv(REQUEST_URI)); // returns the whole URI (including
parms) in UTF-8

My server has the directive DefaultNetCCSID 1208

Is there any explanation of this?


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.