× 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.



Apply PTF SI27738.

Note - I bit of googling throws up comments about TEXT/XML being deprecated
and some conjecture as to whether this is a Microsoft or Apache issue.

It'll never happen :-)

HTH,
Aaron Bartell
Lead developer of RPG-XML Suite (www.rpg-xml.com)

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Peter Connell
Sent: Thursday, September 13, 2007 5:52 PM
To: RPG400-L@xxxxxxxxxxxx
Subject: QtmhRdStin at V5R4

Hi,

Having just upgraded from V5R2 to V5R4 we had a problem with the certain CGI
apps where calls from RPG to the QtmhRdStin API now return blanks.
However, it worked OK in other CGI apps which also use QtmhRdStin.

My investigation shows that it appears that the problem relates to the HTTP
request header being received by the Apache HTTP server, namely when it
contains the header entry CONTENT-TYPE: TEXT/XML; CHARSET=UTF-8

While this has always worked OK at V5R2, it would appear that Apache at
V5R4 does not handle this header as expected.
When the HTTP client is a browser, the problem arises when the browser sends
a request using the Microsoft.XMLHTTP control, but only when the xml
payload has a data type that is a document. NOTE - a payload which is
formatted as a string works fine.

So it appears that sending an xml document created via the Microsoft.XMLDOM
control will generate an http header with a content type of text/xml which
Apache does not like.

However, having confirmed that the problem still occurs when reading STDIN
directly from RPG via the read API, provided via QC2LE, then it may be
reasonable to suspect that any CGI application will suffer from this
affliction when passed a header with a content type of text/xml.

I can work around the problem for browser based requests by ensuring that
the payload is a string instead of a DOM document, but it would be
preferable if there was a way to alter the Apache HTTP configuration to
accomodate this. I have tried various Addtype directives and attempted a
rewrite rule by to no avail.
Has anyone else had a solve this?

Note - I bit of googling throws up comments about TEXT/XML being deprecated
and some conjecture as to whether this is a Microsoft or Apache issue.

Cheers, Peter



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.