To my knowledge an IFS file is encoded based on the code page of the folder where it is created/stored.
I don’t think the api will be able to change that, as far as I understand.
We currently have a method to pass “reports” to a web app…
Currently we (from the ibmi) send an email, with the report (be it a pdf, or xml, text, spreadsheet)
The old process would listen for an email, and import the attachment into the report vault.
I am now asked to change that process to send a web request, attaching the ifs file…
I am told “you should be able to encode the attachment, like you do on sending a email” to the web call.
Does Httpapi have this?
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
_______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxx http://scottklement.com/mailman/listinfo/ftpapi