I'm trying to run the code below which is supposed to create an error. The 2nd parameter of the QSYS2.HTTP_POST command is blank. The header authorization is also blank. I'm expecting an error such as 'No access token provided' to appear in my response file upu178shiprm.txt.

Instead, I get what appears to be garbage in my response file upu178shiprm.txt which is pasted below.

The replystmf is defined as a clob_file. I've also defined replystmf as 'sqltype(clob_file) ccsid(1208)' and 'sqltype(clob_file) ccsid(37)'.

D replystmf       s                   sqltype(clob_file)

Does anyone have any thoughts on what is causing the unreadable response and what needs to be done to correct it?

I have other code where I'm successfully retrieving an authorization token from Fedex, sending the authorization token and data to the Fedex Ship API below, and still receiving an unreadable response. It's a different response than what is pasted below but still unreadable.

Any help would be appreciated. Thanks, Doug.

0182.00  /free
0183.00   replystmf_Name = '/xxxxxxxx/upu178shiprm.txt';
0184.00   replystmf_NL   = %len(%trimr(replystmf_name));
0185.00   replystmf_FO   = SQFOVR;
0186.00    Exec Sql
0187.00     VALUES QSYS2.HTTP_POST(
0188.00               'https://apis-sandbox.fedex.com/ship/v1/shipments',
0189.00                ' ',
0190.00               '{"headers":{'
0191.00               || '"content-type":"application/json",'
0192.00               || '"authorization":" ",'
0193.00               || '"ssltolerate":"true",'
0194.00               || '"x-locale":"en-US"'
0195.00               || '}}')
0196.00               into :replystmf;
0197.00  /end-free
0198.00 C*

Fedex Response (upu178shiprm.txt)

‹      ÿÊÁ
‚@ Ð_æœ"¦äz
ò'!v):L»£H¹[»k â¿'¼½%íHúÞèRa(„ŒHì8H3±
'8‚,‰·"´ªe'    …dku˜ßf"F1æxªšpiŽU]^‹CXÔuU¯q`ç¨û $åJðæÉÞÖ|{Å*„ó‹É1 Fõí"-XþŒì<VàíÔQ¯C\îËYZö›´  

Sorry  Anton, didn't see your post until I responded (still early here 😉).
Yes, what Anton said 😁

I didn't go past confirming the original problem 🤪
Didn't try to figure out if there's some sort of issue in the SQL or axis programs, and didn't check for existing solutions.
The problem is understood, so an issue/idea and a workaround should be within reach 😁

The response is GZIPed, so it's binary (a blob, not a clob).
Tried requesting an uncompressed response ("Accept-Encoding": "identity") but FedEx did not comply.
Unrelated issue is that sslTolerate is not a header and should be included in the "options" parm but not inside "headers" object.  Also, true (the Boolean) is not the same at "true" the string.
Also unrelated but sslTolerate is OK for a little testing but please get the certificate installed and validate.

We can download the binary response:
call ifs_write_binary( 
    path_name => '/some/path/test_fedex_blob.json.gzip',
    line => (
        values qsys2.http_post_blob(
            url => 'https://apis-sandbox.fedex.com/ship/v1/shipments',
            request_message => '',
            options => '{"sslTolerate":true, "headers":{"content-type":"application/json", "authorization":"", "x-locale":"en-US", "Accept-Encoding": "identity"}}'
        )
    )
)

And then if you gunzip that (i.e. in bash), you'll get the JSON file.

Thank you Anton, Patrick, and John (privately) for responding.

I wanted to follow up. I added the following header line to my code:

                                    || '"content-encoding":"gzip",'

and I can receive a readable response from Fedex which I've pasted below. I believe I've been getting this 'Invalid GZIP' message all along but have not been able to read it. I captured the axis.log yesterday and it showed a HTTP 400 Bad Request so I have work to do.

Thanks again for the help. Doug.

 <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
        <soapenv:Fault>
            <faultcode>soapenv:Server</faultcode>
            <faultstring>Invalid GZIP compressed request</faultstring>
            <faultactor>https://apis-sandbox.fedex.com:443/ship/v1/shipments</faultactor>
        </soapenv:Fault>
    </soapenv:Body>
</soapenv:Envelope>

(removed my previous answer as the https was included).

BTW, it seems that Fedex is ignoring Accept-Encoding and Accept headers so the only solution is to unzip the reply.

PS. /free and /end-free are no longer required in RPG.