| |
Retrieve web resources, upload data, and submit requests to web
services using HTTP or HTTPS. The control provides both convenient
transfer methods and direct control over requests, headers,
authentication, and response data for applications that work with web
servers and REST APIs.
Reference
Control Information
| Object Name |
HttpClientCtl.HttpClient |
| File Name |
CSHTPX12.OCX |
| Version |
12.0.3041.1380 |
| ProgID |
SocketTools.HttpClient.12 |
| ClassID |
4D8A16DE-6F64-47A4-99C2-6BEA00228341 |
| Threading Model |
Apartment |
| Help File |
CST12CTL.CHM |
| Dependencies |
None |
| Standards |
RFC 1945, RFC 2616, RFC 7230, RFC 7540 |
Overview
The HttpClient ActiveX control provides
methods for retrieving web resources, uploading files, and
exchanging data with web applications and services. High-level
methods handle common transfers using local files, memory buffers,
or strings, while lower-level methods allow applications to
send custom commands and read or write data directly. Extended
file transfer functions support resources larger than 4 GiB.
For web service integration, the control includes methods for
submitting JSON, XML, and plain text, issuing PATCH requests, and
sending requests with application-defined methods and content.
Applications can specify content types, add custom request headers,
and inspect response headers and status codes. The library handles the
HTTP exchange, while the application interprets the returned content
according to the service or resource being accessed.
Virtual form methods allow applications to assemble fields and
file attachments and submit them to a server for processing. Cookie
management properties provide access to values used to maintain
application state, and authentication functions support restricted
resources. The control also supports OAuth 2.0 bearer token
authentication for accessing protected web services and resources.
Applications are responsible for obtaining and refreshing access
tokens using the authorization process required by the service, while
the control handles their use when making authenticated requests.
Applications can also inspect redirect destinations, specify the user
agent string, and enable support for compressed responses.
The control supports HTTP/1.0, HTTP/1.1, HTTP/2, and HTTP/3, along
with proxy connections and secure connections using TLS 1.2 or later.
Client certificates can be supplied when required by the server.
Configurable timeouts, detailed result information, and optional
network tracing assist with troubleshooting. The control also supports
WebDAV operations for managing remote resources, including creating
collections, copying, moving, and deleting files and directories.
These operations depend on the capabilities of the server and the
access permissions granted to the application.
Requirements
The SocketTools ActiveX Edition components are self-registering
controls that are compatible with any programming language that
supports the Component Object Model (COM) and the ActiveX control
specification. If you are using Visual Basic 6.0, Service Pack 6 (SP6)
is required. We recommend installing all available updates for your
development tools. Although the Visual Basic 6.0 runtime is supported
on Windows 11, the IDE itself is no longer officially supported by
Microsoft. Legacy IDEs and compilers may also require elevated
(administrator) privileges to run properly.
The ActiveX controls are supported on Windows 7, Windows Server
2008 R2, and later versions of both desktop and server editions of
Windows. For Windows 7, Service Pack 1 (SP1) is the minimum
requirement. For Windows 8 systems, the 8.1 update must be installed.
On ARM-based platforms, the minimum supported version is Windows 10
build 1709.
SocketTools includes components for both 32-bit (x86) and 64-bit
(x64) Windows platforms. All modern versions of Windows are 64-bit,
but we continue to include 32-bit components for compatibility with
legacy development tools such as Visual Basic 6.0. We also provide
native ARM64 ActiveX controls for systems running Windows on ARM. Note
that 32-bit applications on ARM run using x86 emulation, and Microsoft
no longer supports native ARM32 applications.
If you are using VBScript, Visual Basic for Applications (VBA), or
another scripting environment on an ARM-based system, be aware that
64-bit hosts will require ARM64 components, while 32-bit hosts will
use x86 components under emulation. This includes applications created
with Visual Basic 6.0. To reduce deployment complexity and avoid
confusion, SocketTools does not include ARM32 ActiveX controls in its
standard redistribution packages but they are available on request for
legacy or specialized scenarios.
Distribution
When distributing an application which uses this control, you can
either install the OCX file as a shared component in the appropriate
system folder or in the same folder as your application executable. If
the control is installed in a shared system location, the installer
should manage it as a shared component to prevent other applications
from being affected when it is updated or removed. If you install the
control in the same folder as your executable, it is recommended that
you use registration-free activation or COM redirection to ensure that
the correct version of the control is loaded by the application.
This control has no external runtime dependencies beyond the
standard Windows system libraries. It does not require the Microsoft
Visual C++ Redistributable or any additional third-party libraries to
be installed. All required components are either provided by Windows
or statically linked into the ActiveX control, simplifying deployment
and eliminating the need to distribute additional runtime files.
|
|