Back to product page
- Introduction
- License agreement
- Classes
- Enumerations
- Exceptions
- WeOnlyDo.Server.WebServer
- WeOnlyDo.Server.WebHeader
- WeOnlyDo.Server.WebHeaders
- WeOnlyDo.Server.WebRequest
- WeOnlyDo.Server.WebResponse
- WeOnlyDo.Server.WebSessions
- WeOnlyDo.Server.WebSessionVar
- WeOnlyDo.Server.WebSessionVars
- WeOnlyDo.Server.WebUpload
- WeOnlyDo.Server.WebUploads
- WeOnlyDo.Server.WebUser
- WeOnlyDo.Server.WebUsers
- How to get support?
RequestHeadersDoneEvent event
Fires when wodWebServer.NET receives request headers from the user.
Syntax
- C#
- VB.NET
delegate void RequestHeadersDoneDelegate(object Sender, WebRequestHeadersDoneArgs Args);
The RequestHeadersDoneEvent(Args.Request,Args.Response,Args.User) syntax has these parts:
The RequestHeadersDoneEvent(Args.Request,Args.Response,Args.User) syntax has these parts:
Args.Request | WebRequest object. Provides reference to request that was made by the client. |
Args.Response | WebResponse object. Response that is being served to client. |
Args.User | WebUser object. Reference to the user who is connected to the server. |
Delegate Sub RequestHeadersDoneDelegate(ByVal Sender as Object, ByVal Args As WebRequestHeadersDoneArgs)RequestHeadersDoneEvent
The RequestHeadersDoneEvent(Args.Request,Args.Response,Args.User) syntax has these parts:
The RequestHeadersDoneEvent(Args.Request,Args.Response,Args.User) syntax has these parts:
Args.Request | WebRequest object. Provides reference to request that was made by the client. |
Args.Response | WebResponse object. Response that is being served to client. |
Args.User | WebUser object. Reference to the user who is connected to the server. |
Remarks
RequestHeaders is fired after connected user sends request headers, but before any body content is sent - if any will be sent at all. This place is convenient for determining if user is about to upload files so you can prepare yourself and setup Request.Stream property to some exact location (otherwise, wodWebServer.NET will save received body to temporary MemoryStream). If you plan to support PUT methods of HTTP protocol, you might want to use this event to point directly to location where file will be saved.But this is not it's only purpose. You have full access to Request.Headers at this point - and it tells you quite a bit about body content that is about to arrive.