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
HeadersDone event
Fires when wodHttpDLX finishes receiving headers.
Syntax
- Basic
Private Sub object_HeadersDone()
The HeadersDone(object) syntax has these parts:
The HeadersDone(object) syntax has these parts:
object | A wodHttpDLX object. |
Remarks
The HTTP protocol works in a way such that every document that is sent or retrieved has several headers describing the document. Some of them are for the client's use, and some of them provide specific details to the user about the received document. At this point you can be aware of the name for the document that is to be downloaded, and, for example, setup Response.Filename property so it points to a location on the disk where document should be stored. This event is fired when all headers have arrived. The user should refer to them if he needs some particular information about the received document. The wodHttpDLX control does not interfere with sent or received headers, except these:-
Content-Length
Content-Type
Connection/Proxy-Connection
Host