This works fine!
I could not "put" to your URL, because it gives me an error:
"(GSKit) Access to the key database is not allowed. "
But, I have tested it with my own rest server, and it works!
Thanks again
Search found 4 matches
- Sat Dec 11, 2021 11:03 am
- Forum: HTTPAPI
- Topic: HTTPAPI & UTF-8 strings
- Replies: 8
- Views: 23002
Re: HTTPAPI & UTF-8 strings
Thanks Scott.
This works fine!
I could not "put" to your URL, because it gives me an error:
"(GSKit) Access to the key database is not allowed. "
But, I have tested it with my own rest server, and it works!
Thanks again
This works fine!
I could not "put" to your URL, because it gives me an error:
"(GSKit) Access to the key database is not allowed. "
But, I have tested it with my own rest server, and it works!
Thanks again
- Fri Dec 10, 2021 3:24 pm
- Forum: HTTPAPI
- Topic: HTTPAPI & UTF-8 strings
- Replies: 8
- Views: 23002
Re: HTTPAPI & UTF-8 strings
Ok,
Is there any other procedure in httpapi that can handle utf8 strings in the same way that http_req do?
Is there any other procedure in httpapi that can handle utf8 strings in the same way that http_req do?
- Fri Dec 10, 2021 8:26 am
- Forum: HTTPAPI
- Topic: HTTPAPI & UTF-8 strings
- Replies: 8
- Views: 23002
Re: HTTPAPI & UTF-8 strings
Hi Scott: I have tried it many ways... The definition of "profile" is like this: dcl-ds profile qualified; name varchar(100) ccsid(*utf8); end-ds; The JSON is generated OK. I have tried to send it to the server with SQL, and it works perfectly. The problem is, I think, with the http_setOpt...
- Wed Dec 08, 2021 11:14 am
- Forum: HTTPAPI
- Topic: HTTPAPI & UTF-8 strings
- Replies: 8
- Views: 23002
HTTPAPI & UTF-8 strings
Hi all: I'm having problems sending utf-8 strings to a rest server using http_req. I'm not sure if I'm doing it well: I have a pf with dds like this: UNIQUE R RTEXT1 LANG 1A NUMBER 5S 0 TEXT 50G CCSID(1200 *NOCONVERT) K LANG K NUMBER TEXT. contains data in different languages (spanish, engligh, russ...