Back to product page
- Introduction
- License agreement
- Getting Started
- Objects
- Enumerations
- wodHttpDLX
- Methods
- Properties
- Authentication
- AutoRedirect
- BindIP
- Blocking
- CertErrors
- Certificate
- Compression
- Hostname
- HTTPversion
- IgnoreCertErrors
- KeepAlive
- LastError
- LastErrorText
- LocalCertBag
- Login
- MyHostname
- MyIP
- Notification
- Password
- Port
- ProxyAuthentication
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- Request
- Response
- Secure
- Socket
- SSLCipherList
- State
- Timeout
- URL
- UseIPv6
- Version
- Events
- wodHttpNotify
- HttpCookie
- HttpCookies
- HttpHeader
- HttpHeaders
- HttpRequest
- HttpRequestFormPost
- HttpRequestFormUpload
- HttpResponse
- How to get support?
- Technical information
- Fast notifications interface
- Error list
WeOnlyDo! COM Http DLX Client ActiveX Control Introduction
General information
WeOnlyDo Software's wodHttpDLX is a HTTP client ActiveX control that provides easy, both high and low level access to the complete HTTP protocol. It's primary purpose is to retrieve document and other resources from the WEB. It was designed to be as programmer-friendly as possible. You will find it can be fully automated to get you requested resource, but also can be used by advanced programmers under complete control from your code.
Usage model
Default behavior of wodHttpDLX is to do as much as possible to get resource you request - it will automatically connect, try to pass through proxy server (if set), try to authenticate with both proxy and the server, follow redirections,..., until it finally grabs requested resource, and then it will disconnect. If the problem occurs during this automation, you will receive notification about failure, so you can request the resource again using different information provided.
Or..
You can use wodHttpDLX to manually connect to the server, send request, check received response, parse received data by yourself - almost all aspect of HTTP protocol is covered by wodHttpDLX. You can have full control over it's behavior if needed - it's all up to you to decide which path you will go.
Features include
* Supports all known and unknown request methods: Get, Post, Put, Delete,...., and you can even use your custom ones
* Besides HTTP requests, it can also handle secured SSL/TLS requests
* Supports many different proxies, including Socks, MSProxy, Squid ...
* Can authenticate both on Proxy, and on protected WEB pages
* Can use GZip and ZLib compression on the fly - giving you up to 80% speed increase
* Supports Basic, NTLM, and Digest authentications
* In SSL mode it can also authenticate using client certificate
* Has separate Request and Response objects
* Can Resume downloads through "Partial Content" responses
* Has interface to help you post and upload data to the server - with ease!
* Provides access to retrieved resource through string property, but also through file on the disk
* Supports blocking and non-blocking mode
* Allows direct interaction with headers - you can check and set Cookies with just one line
* Support cookies, both for Request and Response objects
* Can use proxy settings as defined in Internet Explorer
* .....
Can be used in VB, Delphi, VBS, ASP...
Due to wodHttpDLX'es support both for blocking and non-blocking (event driven) model, you can use wodHttpDLX in virtually any environment. You can decide if you will use COM object or ActiveX - interface is the same, behavior is the same.
And, of course, it's a royalty free component.