Chilkat v11.6.0 / v11.6.1 Release Notes
See Release Notes for Versions 11.6.0 and 11.6.1
See Release Notes for Versions 11.6.0 and 11.6.1
✨ New Features HttpCurl A new Chilkat class has been added: HttpCurl The Chilkat.HttpCurl class executes curl commands and can automatically resolve dependent values needed by a request. Variables such as {{access_token}}, {{site_id}}, or {{drive_id}} may appear in URLs, headers, query parameters, or request bodies. If a variable is not yet known, HttpCurl builds […]
✨ New Features Js A new Chilkat class has been added: Js is a minimal, standards-compliant JavaScript engine designed to embed JavaScript inside applications with very small footprint and fast startup. It executes JavaScript code inside an application without requiring a browser or large runtime. See About the Chilkat.Js JavaScript Engine Ai Provider — […]
What’s going on w/ Chilkat support today… 1. Long HTTP request headers present a difficulty because some web servers choke on header fields that are too long and require folding, whereas others choke on folded headers. Given that HTTP requests are MIME, and the request/response headers are MIME headers, header folding follows the MIME specification. […]
What’s going on with Chilkat support today… 1. The Http.PostJson, PostJson2, and PostJson3 methods neglect to send a Content-Type header if a completely empty body is sent. Starting in the next version (v9.5.0.90) Chilkat will always send the Content-Type header for these methods even if the JSON body is completely empty (i.e. a zero-length string […]
What’s going on with Chilkat support today…. 1. Encountered SMTP response of “503: Bad sequence of commands”. This happened when attempting to use STARTTLS on a server where STARTTLS was not enabled. The port in use is 587, which is the traditional SMTP port for explicit TLS. (Explicit TLS is where the initial connection […]
Chilkat is going to try to blog daily notes on issues we’re handling for customers. So… starting for today.. Suddenly SOAP XML posts to the Brasilian tax server https://nfce.sefazrs.rs.gov.br/ws/NfeAutorizacao/NFeAutorizacao4.asmx stop working with a 415 response code having error “The server cannot service the request because the media type is unsupported.”. The error “media type is […]
A Chilkat customer is signing PDFs and then validating using the online tool at https://ec.europa.eu/cefdigital/DSS/webapp-demo/validation A few errors/warnings were encountered: 1) “The signature is not intact”. <b>This error only happens if the “ltvOcsp” option was set</b> to create an LTV-enabled signature. The source of the “Signature is not intact” error can be found here: https://github.com/esig/dss/blob/master/validation-policy/src/main/java/eu/europa/esig/dss/validation/process/bbb/cv/checks/SignatureIntactCheck.java […]
Chilkat has received email from customers asking to support PureBasic on M1 Apple silicon and Raspberry Pi. This is no problem for Chilkat. We can easily produce the required native .so, .dylib, etc. for each architecture. We only need documentation from PureBasic about these new architectures. For example, what are the compiler directives to choose? […]
The previous version release notes: Chilkat v9.5.0.88 Release Notes Chilkat v9.5.0.89 Release Notes Http: Integrated Amazon Pay authentication into the Chilkat HTTP API to eliminate the need for the application developer to directly implement the computations for canonical request and signature. Http: Integrated Duo Security Multi-Factor Authentication (MFA) into the Chilkat HTTP API to eliminate […]
Here’s a snippet of C# code to do AES encryption. What is the equivalent in Chilkat? Dim cspRijndael As New System.Security.Cryptography.RijndaelManaged csCryptoStream = New CryptoStream(fsOutput, cspRijndael.CreateEncryptor(bytKey, bytIV), CryptoStreamMode.Write) “Rijndael” is the name of the encryption algorithm, and (essentially) “AES” is Rijndael limited to the choices of 128, 192, or 256 bits. Rijndael/AES is a symmetric […]
Question: How can JSON be processed in a case-insensitive manner? Rant followed by Answer: JSON is intended to be case-sensitive. XML is the same. Similar to Java, C, C++, etc. Names are case-sensitive. Except, of course, there are knuckleheads out there that don’t understand the fundamental specifications and as a result introduce complexity into systems […]
(Chilkat is going to begin posting about the ongoing work with customers involving smart cards and tokens used for signing PDFs and XML invoices, etc.) The links below are to examples that create a .p7m signature for an Italian e-Invoice (FatturaPA) using a private key stored on a smart card. It duplicates the following OpenSSL […]