This is less RPG-related, and more HTTP-related (I am not a web--
I'm working with a new API (as a consumer). Their documentation
states that the Authorization part of the header should be:
Authorization Basic MTIzNDU6YWJjZGU=
The characters after basic represent "The application ID and shared
secret must be concatenated using a colon then RFC2045-MIME (base-64) encoded."
(in this case 12345:abcde)
So I did the concatenation and base64_encode in my program BEFORE
using the HTTP_SETAUTH procedure of HTTPAPI. After reviewing the
debug.txt file, I could clearly see that HTTP_SETAUTH does that for me
(I was basically encoding the "user" and "password" only to have
HTTP_SETAUTH do it again)
This code works just fine:
rc = http_setauth(HTTP_AUTH_BASIC : applicationID : sharedSecret);
I would just like to understand how http_setauth "knows" to encode these.
Is that an HTTP/HTTPS standard?
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate