Releases: Dyalog/HttpCommand
Releases · Dyalog/HttpCommand
v5.1.3
Version 5.1.3
-
Added proxy server support. See Proxy-related Settings and Using a Proxy Server.
-
Changed how HttpCommand attempts to determine payload Content-Type if the user has not specified it.
- Prior behavior was to always treat it as x-www-form-urlencoded.
- Now, HttpCommand will use a Content-Type of application/json;charset=utf-8 if the payload either:
- is simple and looks like JSON
- is a set of name/value pairs
To avoid having HttpCommand "guess" improperly, set Content-Type explicitly.
-
If Auth is either a vector in form 'userid:password' or a 2-element vector ('userid' 'password') and AuthType is either unspecified or 'basic', HttpCommand will properly Base64Encode the credentials for HTTP Basic authentication.
v5.0.7
v5.0.6
First release in the new HttpCommand repository.
Version 5.0
- The major version bump from 4 to 5 was due to:
- swapping the meaning for the
TimeoutandWaitTimesettings. PreviouslyTimeoutwas used to indicate how long Conga'sWaitfunction would wait for a response andWaitTimewas how longHttpCommandwould wait for a complete response before timing out. - return codes and messages were normalized
- swapping the meaning for the
- Added new
AuthandAuthTypesettings to more easily support token-based authentication. - Removed half-implemented support for streaming
- Added
GetHeaderfunction to result namespace - More complete setting checking
- Better handling of relative redirections
- New documentation