From 1dc09d8e8f4a6caa321d0227722af97ee4aeed6a Mon Sep 17 00:00:00 2001
From: teravus
Date: Tue, 5 Feb 2013 18:02:25 -0500
Subject: We're not really done here.. but we're getting there. Socket Read
is working.. Still have to do Header.ToBytes and compose a websocket frame
with a payload.
---
.../Framework/Servers/HttpServer/BaseHttpServer.cs | 38 +-
OpenSim/Framework/Servers/Tests/OSHttpTests.cs | 5 +
.../TCPJSONStream/OpenSimWebSocketBase.cs | 6 +-
bin/HttpServer_OpenSim.dll | Bin 115712 -> 116224 bytes
bin/HttpServer_OpenSim.pdb | Bin 413184 -> 302592 bytes
bin/HttpServer_OpenSim.xml | 6398 ++++++++++----------
6 files changed, 3244 insertions(+), 3203 deletions(-)
diff --git a/OpenSim/Framework/Servers/HttpServer/BaseHttpServer.cs b/OpenSim/Framework/Servers/HttpServer/BaseHttpServer.cs
index b24336d..dcfe99a 100644
--- a/OpenSim/Framework/Servers/HttpServer/BaseHttpServer.cs
+++ b/OpenSim/Framework/Servers/HttpServer/BaseHttpServer.cs
@@ -54,6 +54,8 @@ namespace OpenSim.Framework.Servers.HttpServer
private static readonly ILog m_log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);
private HttpServerLogWriter httpserverlog = new HttpServerLogWriter();
+ public delegate void WebSocketRequestDelegate(string servicepath, WebSocketHTTPServerHandler handler);
+
///
/// Gets or sets the debug level.
///
@@ -87,6 +89,9 @@ namespace OpenSim.Framework.Servers.HttpServer
protected Dictionary m_pollHandlers =
new Dictionary();
+ protected Dictionary m_WebSocketHandlers =
+ new Dictionary();
+
protected uint m_port;
protected uint m_sslport;
protected bool m_ssl;
@@ -170,6 +175,22 @@ namespace OpenSim.Framework.Servers.HttpServer
}
}
+ public void AddWebSocketHandler(string servicepath, WebSocketRequestDelegate handler)
+ {
+ lock (m_WebSocketHandlers)
+ {
+ if (!m_WebSocketHandlers.ContainsKey(servicepath))
+ m_WebSocketHandlers.Add(servicepath, handler);
+ }
+ }
+
+ public void RemoveWebSocketHandler(string servicepath)
+ {
+ lock (m_WebSocketHandlers)
+ if (m_WebSocketHandlers.ContainsKey(servicepath))
+ m_WebSocketHandlers.Remove(servicepath);
+ }
+
public List GetStreamHandlerKeys()
{
lock (m_streamHandlers)
@@ -409,9 +430,24 @@ namespace OpenSim.Framework.Servers.HttpServer
public void OnHandleRequestIOThread(IHttpClientContext context, IHttpRequest request)
{
+
OSHttpRequest req = new OSHttpRequest(context, request);
+ WebSocketRequestDelegate dWebSocketRequestDelegate = null;
+ lock (m_WebSocketHandlers)
+ {
+ if (m_WebSocketHandlers.ContainsKey(req.RawUrl))
+ dWebSocketRequestDelegate = m_WebSocketHandlers[req.RawUrl];
+ }
+ if (dWebSocketRequestDelegate != null)
+ {
+ dWebSocketRequestDelegate(req.Url.AbsolutePath, new WebSocketHTTPServerHandler(req, context, 16384));
+ return;
+ }
+
OSHttpResponse resp = new OSHttpResponse(new HttpResponse(context, request),context);
+
HandleRequest(req, resp);
+
// !!!HACK ALERT!!!
// There seems to be a bug in the underlying http code that makes subsequent requests
@@ -500,7 +536,7 @@ namespace OpenSim.Framework.Servers.HttpServer
LogIncomingToStreamHandler(request, requestHandler);
response.ContentType = requestHandler.ContentType; // Lets do this defaulting before in case handler has varying content type.
-
+
if (requestHandler is IStreamedRequestHandler)
{
IStreamedRequestHandler streamedRequestHandler = requestHandler as IStreamedRequestHandler;
diff --git a/OpenSim/Framework/Servers/Tests/OSHttpTests.cs b/OpenSim/Framework/Servers/Tests/OSHttpTests.cs
index 3412e0f..5b912b4 100644
--- a/OpenSim/Framework/Servers/Tests/OSHttpTests.cs
+++ b/OpenSim/Framework/Servers/Tests/OSHttpTests.cs
@@ -70,6 +70,11 @@ namespace OpenSim.Framework.Servers.Tests
public void Close() { }
public bool EndWhenDone { get { return false;} set { return;}}
+ public HTTPNetworkContext GiveMeTheNetworkStreamIKnowWhatImDoing()
+ {
+ return new HTTPNetworkContext();
+ }
+
public event EventHandler Disconnected = delegate { };
///
/// A request have been received in the context.
diff --git a/OpenSim/Region/ClientStack/TCPJSONStream/OpenSimWebSocketBase.cs b/OpenSim/Region/ClientStack/TCPJSONStream/OpenSimWebSocketBase.cs
index 379438d..6d02543 100644
--- a/OpenSim/Region/ClientStack/TCPJSONStream/OpenSimWebSocketBase.cs
+++ b/OpenSim/Region/ClientStack/TCPJSONStream/OpenSimWebSocketBase.cs
@@ -47,7 +47,7 @@ namespace OpenSim.Region.ClientStack.TCPJSONStream
public void NetworkStop()
{
- m_tcpServer.Stop();
+ // m_tcpServer.Stop();
}
public bool HandlesRegion(Location x)
@@ -62,12 +62,12 @@ namespace OpenSim.Region.ClientStack.TCPJSONStream
public void Start()
{
- m_tcpServer.Start();
+ //m_tcpServer.Start();
}
public void Stop()
{
- m_tcpServer.Stop();
+ // m_tcpServer.Stop();
}
}
}
\ No newline at end of file
diff --git a/bin/HttpServer_OpenSim.dll b/bin/HttpServer_OpenSim.dll
index d910bb9..9cd1e08 100755
Binary files a/bin/HttpServer_OpenSim.dll and b/bin/HttpServer_OpenSim.dll differ
diff --git a/bin/HttpServer_OpenSim.pdb b/bin/HttpServer_OpenSim.pdb
index b9161e1..d20a0c5 100644
Binary files a/bin/HttpServer_OpenSim.pdb and b/bin/HttpServer_OpenSim.pdb differ
diff --git a/bin/HttpServer_OpenSim.xml b/bin/HttpServer_OpenSim.xml
index d31bcca..fa88fc7 100644
--- a/bin/HttpServer_OpenSim.xml
+++ b/bin/HttpServer_OpenSim.xml
@@ -4,547 +4,659 @@
HttpServer_OpenSim
-
-
- A session store is used to store and load sessions on a media.
- The default implementation () saves/retrieves sessions from memory.
-
-
-
+
- Creates a new http session with a generated id.
+ Delegate used to find a realm/domain.
- A object
+
+
+
+ Realms are used during HTTP Authentication
+
+
+
-
+
- Creates a new http session with a specific id
+ A complete HTTP server, you need to add a module to it to be able to handle incoming requests.
- Id used to identify the new cookie..
- A object.
-
- Id should be generated by the store implementation if it's null or .
-
+
+
+ // this small example will add two web site modules, thus handling
+ // two different sites. In reality you should add Controller modules or something
+ // two the website modules to be able to handle different requests.
+ HttpServer server = new HttpServer();
+ server.Add(new WebSiteModule("www.gauffin.com", "Gauffin Telecom AB"));
+ server.Add(new WebSiteModule("www.vapadi.se", "Remote PBX"));
+
+ // start regular http
+ server.Start(IPAddress.Any, 80);
+
+ // start https
+ server.Start(IPAddress.Any, 443, myCertificate);
+
+
+
+
+
-
+
- Load an existing session.
+ Initializes a new instance of the class.
- Session id (usually retrieved from a client side cookie).
- A session if found; otherwise null.
+ Used to get all components used in the server..
-
+
- Save an updated session to the store.
+ Initializes a new instance of the class.
- Session id (usually retrieved from a client side cookie).
- If Id property have not been specified.
-
+
- We use the flyweight pattern which reuses small objects
- instead of creating new each time.
+ Initializes a new instance of the class.
- Unused session that should be reused next time Create is called.
+ Form decoders are used to convert different types of posted data to the object types.
+
+
-
+
- Remove expired sessions
+ Initializes a new instance of the class.
+ A session store is used to save and retrieve sessions
+
-
+
- Remove a session
+ Initializes a new instance of the class.
- id of the session.
+ The log writer.
+
-
+
- Load a session from the store
+ Initializes a new instance of the class.
-
- null if session is not found.
+ Form decoders are used to convert different types of posted data to the object types.
+ The log writer.
+
+
+
-
+
- Number of minutes before a session expires.
+ Initializes a new instance of the class.
- Default time is 20 minutes.
+ Form decoders are used to convert different types of posted data to the object types.
+ A session store is used to save and retrieve sessions
+ The log writer.
+
+
+
+
-
+
- Contains server side HTTP request information.
+ Adds the specified rule.
+ The rule.
-
+
- Called during parsing of a .
+ Add a to the server.
- Name of the header, should not be URL encoded
- Value of the header, should not be URL encoded
- If a header is incorrect.
+ mode to add
-
+
- Add bytes to the body
+ Decodes the request body.
- buffer to read bytes from
- where to start read
- number of bytes to read
- Number of bytes actually read (same as length unless we got all body bytes).
- If body is not writable
- bytes is null.
- offset is out of range.
+ The request.
+ Failed to decode form data.
-
+
- Clear everything in the request
+ Generate a HTTP error page (that will be added to the response body).
+ response status code is also set.
+ Response that the page will be generated in.
+ .
+ response body contents.
-
+
- Decode body into a form.
+ Generate a HTTP error page (that will be added to the response body).
+ response status code is also set.
- A list with form decoders.
- If body contents is not valid for the chosen decoder.
- If body is still being transferred.
+ Response that the page will be generated in.
+ exception.
-
+
- Sets the cookies.
+ Realms are used by the s.
- The cookies.
+ HTTP request
+ domain/realm.
-
+
- Create a response object.
+ Process an incoming request.
- Context for the connected client.
- A new .
+ connection to client
+ request information
+ response that should be filled
+ session information
-
+
- Gets kind of types accepted by the client.
+ Can be overloaded to implement stuff when a client have been connected.
+
+ Default implementation does nothing.
+
+ client that disconnected
+ disconnect reason
-
+
- Gets or sets body stream.
+ Handle authentication
+
+
+
+ true if request can be handled; false if not.
+ Invalid authorization header
-
+
- Gets whether the body is complete.
+ Will request authentication.
+
+ Sends respond to client, nothing else can be done with the response after this.
+
+
+
+
-
+
- Gets or sets kind of connection used for the session.
+ Received from a when a request have been parsed successfully.
+ that received the request.
+ The request.
-
+
- Gets or sets number of bytes in the body.
+ To be able to track request count.
+
+
-
+
- Gets cookies that was sent with the request.
+ Start the web server using regular HTTP.
+ IP Address to listen on, use IpAddress.Any to accept connections on all IP addresses/network cards.
+ Port to listen on. 80 can be a good idea =)
+ address is null.
+ Port must be a positive number.
-
+
- Gets form parameters.
+ Accept secure connections.
+ IP Address to listen on, use to accept connections on all IP Addresses / network cards.
+ Port to listen on. 80 can be a good idea =)
+ Certificate to use
+ address is null.
+ Port must be a positive number.
-
+
- Gets headers sent by the client.
+ shut down the server and listeners
-
+
- Gets or sets version of HTTP protocol that's used.
+ write an entry to the log file
-
- Probably or .
-
-
+ importance of the message
+ log message
-
+
- Gets whether the request was made by Ajax (Asynchronous JavaScript)
+ write an entry to the log file
+ object that wrote the message
+ importance of the message
+ log message
-
+
- Gets or sets requested method.
+ Server that is handling the current request.
- Will always be in upper case.
+ Will be set as soon as a request arrives to the object.
-
-
+
- Gets parameter from or .
-
-
-
-
- Gets variables sent in the query string
+ Modules used for authentication. The module that is is added first is used as
+ the default authentication module.
+ Use the corresponding property
+ in the if you are using multiple websites.
-
+
- Gets or sets requested URI.
+ Form decoder providers are used to decode request body (which normally contains form data).
-
+
- Gets URI absolute path divided into parts.
+ Server name sent in HTTP responses.
-
- // URI is: http://gauffin.com/code/tiny/
- Console.WriteLine(request.UriParts[0]); // result: code
- Console.WriteLine(request.UriParts[1]); // result: tiny
-
- If you're using controllers than the first part is controller name,
- the second part is method name and the third part is Id property.
+ Do NOT include version in name, since it makes it
+ easier for hackers.
-
-
+
- Gets or sets path and query.
+ Name of cookie where session id is stored.
-
-
- Are only used during request parsing. Cannot be set after "Host" header have been
- added.
-
-
+
- Class that receives Requests from a .
+ Specified where logging should go.
+
+
+
-
+
- Client have been disconnected.
+ Number of connections that can wait to be accepted by the server.
- Client that was disconnected.
- Reason
-
+ Default is 10.
-
+
- Invoked when a client context have received a new HTTP request
+ Gets or sets maximum number of allowed simultaneous requests.
- Client that received the request.
- Request that was received.
-
+
+
+ This property is useful in busy systems. The HTTP server
+ will start queuing new requests if this limit is hit, instead
+ of trying to process all incoming requests directly.
+
+
+ The default number if allowed simultaneous requests are 10.
+
+
-
+
- Delegate used by to populate select options.
+ Gets or sets maximum number of requests queuing to be handled.
- current object (for instance a User).
- Text that should be displayed in the value part of a <optiongt;-tag.
- Text shown in the select list.
-
- // Class that is going to be used in a SELECT-tag.
- public class User
- {
- private readonly string _realName;
- private readonly int _id;
- public User(int id, string realName)
- {
- _id = id;
- _realName = realName;
- }
- public string RealName
- {
- get { return _realName; }
- }
-
- public int Id
- {
- get { return _id; }
- }
- }
-
- // Using an inline delegate to generate the select list
- public void UserInlineDelegate()
- {
- List<User> items = new List<User>();
- items.Add(new User(1, "adam"));
- items.Add(new User(2, "bertial"));
- items.Add(new User(3, "david"));
- string htmlSelect = Select("users", "users", items, delegate(object o, out object id, out object value)
- {
- User user = (User)o;
- id = user.Id;
- value = user.RealName;
- }, 2, true);
- }
-
- // Using an method as delegate to generate the select list.
- public void UseExternalDelegate()
- {
- List<User> items = new List<User>();
- items.Add(new User(1, "adam"));
- items.Add(new User(2, "bertial"));
- items.Add(new User(3, "david"));
- string htmlSelect = Select("users", "users", items, UserOptions, 1, true);
- }
-
- // delegate returning id and title
- public static void UserOptions(object o, out object id, out object title)
- {
- User user = (User)o;
- id = user.Id;
- value = user.RealName;
- } ///
+
+
+ The WebServer will start turning requests away if response code
+ to indicate that the server
+ is too busy to be able to handle the request.
+
+
-
+
- The server understood the request, but is refusing to fulfill it.
- Authorization will not help and the request SHOULD NOT be repeated.
- If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled,
- it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information
- available to the client, the status code 404 (Not Found) can be used instead.
-
- Text taken from: http://www.submissionchamber.com/help-guides/error-codes.php
+ Realms are used during HTTP authentication.
+ Default realm is same as server name.
-
+
- All HTTP based exceptions will derive this class.
+ Let's to receive unhandled exceptions from the threads.
+
+ Exceptions will be thrown during debug mode if this event is not used,
+ exceptions will be printed to console and suppressed during release mode.
+
-
+
- Create a new HttpException
+ Serves files that are stored in embedded resources.
- http status code (sent in the response)
- error description
-
+
- Create a new HttpException
+ A HttpModule can be used to serve Uri's. The module itself
+ decides if it should serve a Uri or not. In this way, you can
+ get a very flexible http application since you can let multiple modules
+ serve almost similar urls.
- http status code (sent in the response)
- error description
- inner exception
+
+ Throw if you are using a and want to prompt for user name/password.
+
-
+
- status code to use in the response.
+ Method that process the url
+ Information sent by the browser about the request
+ Information that is being sent back to the client.
+ Session used to
+ true if this module handled the request.
-
+
- Initializes a new instance of the class.
+ Set the log writer to use.
- error message
+ logwriter to use.
-
+
- A session stored in memory.
+ Log something.
+ importance of log message
+ message
-
+
- Interface for sessions
+ If true specifies that the module doesn't consume the processing of a request so that subsequent modules
+ can continue processing afterwards. Default is false.
-
+
- Remove everything from the session
+ Initializes a new instance of the class.
+ Runs to make sure the basic mime types are available, they can be cleared later
+ through the use of if desired.
-
+
- Remove everything from the session
+ Initializes a new instance of the class.
+ Runs to make sure the basic mime types are available, they can be cleared later
+ through the use of if desired.
- True if the session is cleared due to expiration
+ The log writer to use when logging events
-
+
- Session id
+ Mimtypes that this class can handle per default
-
+
- Should
+ Loads resources from a namespace in the given assembly to an uri
- Name of the session variable
- null if it's not set
- If the object cant be serialized.
+ The uri to map the resources to
+ The assembly in which the resources reside
+ The namespace from which to load the resources
+
+ resourceLoader.LoadResources("/user/", typeof(User).Assembly, "MyLib.Models.User.Views");
+
+ will make ie the resource MyLib.Models.User.Views.stylesheet.css accessible via /user/stylesheet.css
+
+ The amount of loaded files, giving you the possibility of making sure the resources needed gets loaded
-
+
- When the session was last accessed.
- This property is touched by the http server each time the
- session is requested.
+ Returns true if the module can handle the request
-
+
- Number of session variables.
+ Method that process the url
+ Information sent by the browser about the request
+ Information that is being sent back to the client.
+ Session used to
+ true if this module handled the request.
-
+
- Event triggered upon clearing the session
+ List with all mime-type that are allowed.
+ All other mime types will result in a Forbidden http status code.
-
+
-
+ Contains some kind of input from the browser/client.
+ can be QueryString, form data or any other request body content.
- A unique id used by the sessions store to identify the session
-
+
- Id
+ Base class for request data containers
-
-
+
- Remove everything from the session
+ Adds a parameter mapped to the presented name
+ The name to map the parameter to
+ The parameter value
-
+
- Clears the specified expire.
+ Returns true if the container contains the requested parameter
- True if the session is cleared due to expiration
+ Parameter id
+ True if parameter exists
-
+
- Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.
+ Returns a request parameter
- 2
+ The name associated with the parameter
+
-
+
+ Representation of a non-initialized class instance
+
+
+ Variable telling the class that it is non-initialized
+
+
- Session id
+ Initializes a new instance of the class.
+ form name.
-
+
- Should
+ Initializes a new instance of the class.
- Name of the session variable
- null if it's not set
+ form name.
+ if set to true all changes will be ignored.
+ this constructor should only be used by Empty
-
+
+ Creates a deep copy of the HttpInput class
+ The object to copy
+ The function makes a deep copy of quite a lot which can be slow
+
+
- when the session was last accessed.
+ Add a new element. Form array elements are parsed
+ and added in a correct hierarchy.
-
- Used to determine when the session should be removed.
-
+ Name is converted to lower case.
+
+ name is null.
+ Cannot add stuff to .
-
+
- Number of values in the session
+ Returns true if the class contains a with the corresponding name.
+ The field/query string name
+ True if the value exists
-
+
- Flag to indicate that the session have been changed
- and should be saved into the session store.
+ Parses an item and returns it.
+ This function is primarily used to parse array items as in user[name].
+
+
+
-
+
+ Outputs the instance representing all its values joined together
+
+
+
+ Returns all items as an unescaped query string.
+
+
+
- Event triggered upon clearing the session
+ Extracts one parameter from an array
+ Containing the string array
+ All but the first value
+
+ string test1 = ExtractOne("system[user][extension][id]");
+ string test2 = ExtractOne(test1);
+ string test3 = ExtractOne(test2);
+ // test1 = user[extension][id]
+ // test2 = extension[id]
+ // test3 = id
+
-
+
+ Resets all data contained by class
+
+
- cookie being sent back to the browser.
+ Returns an enumerator that iterates through the collection.
-
+
+
+ A that can be used to iterate through the collection.
+
+ 1
-
+
- cookie sent by the client/browser
+ Returns an enumerator that iterates through a collection.
-
+
+
+ An object that can be used to iterate through the collection.
+
+ 2
-
+
- Constructor.
+ Form name as lower case
- cookie identifier
- cookie content
- id or content is null
- id is empty
-
+
- Gets the cookie HTML representation.
+ Get a form item.
- cookie string
+
+ Returns if item was not found.
-
+
- Gets the cookie identifier.
+ The server understood the request, but is refusing to fulfill it.
+ Authorization will not help and the request SHOULD NOT be repeated.
+ If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled,
+ it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information
+ available to the client, the status code 404 (Not Found) can be used instead.
+
+ Text taken from: http://www.submissionchamber.com/help-guides/error-codes.php
-
+
- Cookie value. Set to null to remove cookie.
+ All HTTP based exceptions will derive this class.
-
+
- Constructor.
+ Create a new HttpException
- cookie identifier
- cookie content
- cookie expiration date. Use DateTime.MinValue for session cookie.
- id or content is null
- id is empty
+ http status code (sent in the response)
+ error description
-
+
- Create a new cookie
+ Create a new HttpException
- name identifying the cookie
- cookie value
- when the cookie expires. Setting DateTime.MinValue will delete the cookie when the session is closed.
- Path to where the cookie is valid
- Domain that the cookie is valid for.
+ http status code (sent in the response)
+ error description
+ inner exception
-
+
- Create a new cookie
+ status code to use in the response.
- Name and value will be used
- when the cookie expires.
-
+
- Gets the cookie HTML representation.
+ Initializes a new instance of the class.
- cookie string
+ error message
-
+
- When the cookie expires.
- DateTime.MinValue means that the cookie expires when the session do so.
+ This class is created as a wrapper, since there are two different cookie types in .Net (Cookie and HttpCookie).
+ The framework might switch class in the future and we dont want to have to replace all instances
-
+
- Cookie is only valid under this path.
+ Let's copy all the cookies.
+
+ value from cookie header.
+
+
+
+ Adds a cookie in the collection.
+
+ cookie to add
+ cookie is null
+
+
+
+ Gets a collection enumerator on the cookie list.
+
+ collection enumerator
+
+
+
+ Remove all cookies.
+
+
+
+
+ Returns an enumerator that iterates through the collection.
+
+
+
+ A that can be used to iterate through the collection.
+
+ 1
+
+
+
+ Remove a cookie from the collection.
+
+ Name of cookie.
+
+
+
+ Gets the count of cookies in the collection.
+
+
+
+
+ Gets the cookie of a given identifier (null if not existing).
@@ -660,102 +772,130 @@
Gets received request.
-
+
- Contains a listener that doesn't do anything with the connections.
+ Returns item either from a form or a query string (checks them in that order)
-
+
+ Representation of a non-initialized HttpParam
+
+
+ Initialises the class to hold a value either from a post request or a querystring request
+
+
- Listen for regular HTTP connections
+ The add method is not availible for HttpParam
+ since HttpParam checks both Request.Form and Request.QueryString
- IP Address to accept connections on
- TCP Port to listen on, default HTTP port is 80.
- Factory used to create es.
- address is null.
- Port must be a positive number.
+ name identifying the value
+ value to add
+
-
+
- Initializes a new instance of the class.
+ Checks whether the form or querystring has the specified value
- IP Address to accept connections on
- TCP Port to listen on, default HTTPS port is 443
- Factory used to create es.
- Certificate to use
+ Name, case sensitive
+ true if found; otherwise false.
-
+
- Initializes a new instance of the class.
+ Returns an enumerator that iterates through the collection.
- IP Address to accept connections on
- TCP Port to listen on, default HTTPS port is 443
- Factory used to create es.
- Certificate to use
- which HTTPS protocol to use, default is TLS.
+
+
+ A that can be used to iterate through the collection.
+
+ 1
-
- Exception.
+
+
+ Returns an enumerator that iterates through a collection.
+
+
+
+ An object that can be used to iterate through the collection.
+
+ 2
-
+
- Will try to accept connections one more time.
+ Fetch an item from the form or querystring (in that order).
- If any exceptions is thrown.
+
+ Item if found; otherwise HttpInputItem.EmptyLanguageNode
-
+
- Can be used to create filtering of new connections.
+ Container class for posted files
- Accepted socket
- true if connection can be accepted; otherwise false.
-
+
- Start listen for new connections
+ Creates a container for a posted file
- Number of connections that can stand in a queue to be accepted.
- Listener have already been started.
+ The identifier of the post field
+ The file path
+ The content type of the file
+ The name of the file uploaded
+ If any parameter is null or empty
-
+
- Stop the listener
+ Creates a container for a posted file
-
+ If any parameter is null or empty
-
+
+ Destructor disposing the file
+
+
- Gives you a change to receive log entries for all internals of the HTTP library.
+ Deletes the temporary file
-
- You may not switch log writer after starting the listener.
-
+ True if manual dispose
-
+
- True if we should turn on trace logs.
+ Disposing interface, cleans up managed resources (the temporary file) and suppresses finalization
-
+
- Catch exceptions not handled by the listener.
+ The name/id of the file
-
- Exceptions will be thrown during debug mode if this event is not used,
- exceptions will be printed to console and suppressed during release mode.
-
-
+
- A request have been received from a .
+ The full file path
-
+
-
+ The name of the uploaded file
+
+
+
+
+ The type of file
+
+
+
+
+ This decoder converts XML documents to form items.
+ Each element becomes a subitem in the form, and each attribute becomes an item.
+
+ // xml: somethingdata
+ // result:
+ // form["hello"].Value = "something"
+ // form["hello"]["id"].Value = 1
+ // form["hello"]["world]["id"].Value = 1
+ // form["hello"]["world"].Value = "data"
+
- http://www.faqs.org/rfcs/rfc1867.html
+ The original xml document is stored in form["__xml__"].Value.
@@ -780,257 +920,237 @@
Content type (with any additional info like boundry). Content type is always supplied in lower case.
True if the decoder can parse the specified content type
-
-
- multipart/form-data
-
-
-
-
- form-data
-
-
-
+
Stream containing the content
Content type (with any additional info like boundry). Content type is always supplied in lower case
- Stream enconding
+ Stream encoding
+ Note: contentType and encoding are not used?
A http form, or null if content could not be parsed.
- If contents in the stream is not valid input data.
- If any parameter is null
+
-
+
+
+ Recursive function that will go through an xml element and store it's content
+ to the form item.
+
+ (parent) Item in form that content should be added to.
+ Node that should be parsed.
+
+
Checks if the decoder can handle the mime type
Content type (with any additional info like boundry). Content type is always supplied in lower case.
True if the decoder can parse the specified content type
-
+
- The requested resource was not found in the web server.
+ The object form class takes an object and creates form items for it.
-
+
- Create a new exception
+ Initializes a new instance of the class.
- message describing the error
- inner exception
+
+ form name *and* id.
+ action to do when form is posted.
+
-
+
- Create a new exception
+ Initializes a new instance of the class.
- message describing the error
+ form name *and* id.
+ action to do when form is posted.
+ object to get values from
-
+
- Delegate used to let authentication modules authenticate the user name and password.
+ Initializes a new instance of the class.
- Realm that the user want to authenticate in
- User name specified by client
- Can either be user password or implementation specific token.
- object that will be stored in a session variable called if authentication was successful.
- throw forbidden exception if too many attempts have been made.
-
-
- Use to specify that the token is a HA1 token. (MD5 generated
- string from realm, user name and password); Md5String(userName + ":" + realm + ":" + password);
-
-
+ form action.
+ object to get values from.
-
+
- Let's you decide on a system level if authentication is required.
+ write out the FORM-tag.
- HTTP request from client
- true if user should be authenticated.
- throw if no more attempts are allowed.
- If no more attempts are allowed
+ generated html code
-
+
- Authentication modules are used to implement different
- kind of HTTP authentication.
+ Writeout the form tag
+ form should be posted through ajax.
+ generated html code
-
+
- Tag used for authentication.
+ Generates a text box.
+
+
+ generated html code
-
+
- Initializes a new instance of the class.
+ password box
- Delegate used to provide information used during authentication.
- Delegate used to determine if authentication is required (may be null).
+
+
+ generated html code
-
+
- Initializes a new instance of the class.
+ Hiddens the specified property name.
- Delegate used to provide information used during authentication.
+ Name of the property.
+ The options.
+ generated html code
-
+
- Create a response that can be sent in the WWW-Authenticate header.
+ Labels the specified property name.
- Realm that the user should authenticate in
- Array with optional options.
- A correct authentication request.
- If realm is empty or null.
+ property in object.
+ caption
+ generated html code
-
+
- An authentication response have been received from the web browser.
- Check if it's correct
+ Generate a checkbox
- Contents from the Authorization header
- Realm that should be authenticated
- GET/POST/PUT/DELETE etc.
- options to specific implementations
- Authentication object that is stored for the request. A user class or something like that.
- if is invalid
- If any of the parameters is empty or null.
-
-
+ property in object
+ checkbox value
+ additional html attributes.
+ generated html code
+
+
- Used to invoke the authentication delegate that is used to lookup the user name/realm.
+ Write a html select tag
- Realm (domain) that user want to authenticate in
- User name
- Password used for validation. Some implementations got password in clear text, they are then sent to client.
- object that will be stored in the request to help you identify the user if authentication was successful.
- true if authentication was successful
+ object property.
+ id column
+ The title column.
+ The options.
+
-
+
- Determines if authentication is required.
+ Selects the specified property name.
- HTTP request from browser
- true if user should be authenticated.
- throw from your delegate if no more attempts are allowed.
- If no more attempts are allowed
+ Name of the property.
+ The items.
+ The id column.
+ The title column.
+ The options.
+
-
+
- name used in HTTP request.
+ Write a submit tag.
+ button caption
+ html submit tag
-
+
- Contains some kind of input from the browser/client.
- can be QueryString, form data or any other request body content.
+ html end form tag
+ html
-
+
- Base class for request data containers
+
+
+ http://www.faqs.org/rfcs/rfc1867.html
+
-
+
- Adds a parameter mapped to the presented name
+ multipart/form-data
- The name to map the parameter to
- The parameter value
-
+
- Returns true if the container contains the requested parameter
+ form-data
- Parameter id
- True if parameter exists
-
+
- Returns a request parameter
+
- The name associated with the parameter
-
-
-
- Representation of a non-initialized class instance
-
-
- Variable telling the class that it is non-initialized
+ Stream containing the content
+ Content type (with any additional info like boundry). Content type is always supplied in lower case
+ Stream enconding
+ A http form, or null if content could not be parsed.
+ If contents in the stream is not valid input data.
+ If any parameter is null
-
+
- Initializes a new instance of the class.
+ Checks if the decoder can handle the mime type
- form name.
+ Content type (with any additional info like boundry). Content type is always supplied in lower case.
+ True if the decoder can parse the specified content type
-
+
- Initializes a new instance of the class.
+ The request could not be understood by the server due to malformed syntax.
+ The client SHOULD NOT repeat the request without modifications.
+
+ Text taken from: http://www.submissionchamber.com/help-guides/error-codes.php
- form name.
- if set to true all changes will be ignored.
- this constructor should only be used by Empty
-
-
- Creates a deep copy of the HttpInput class
- The object to copy
- The function makes a deep copy of quite a lot which can be slow
-
+
- Add a new element. Form array elements are parsed
- and added in a correct hierarchy.
+ Create a new bad request exception.
- Name is converted to lower case.
-
- name is null.
- Cannot add stuff to .
+ reason to why the request was bad.
-
+
- Returns true if the class contains a with the corresponding name.
+ Create a new bad request exception.
- The field/query string name
- True if the value exists
+ reason to why the request was bad.
+ inner exception
-
+
- Parses an item and returns it.
- This function is primarily used to parse array items as in user[name].
+ Cookies that should be set.
-
-
-
-
- Outputs the instance representing all its values joined together
-
+
+
+ Adds a cookie in the collection.
+
+ cookie to add
+ cookie is null
-
- Returns all items as an unescaped query string.
-
+
+
+ Copy a request cookie
+
+
+ When the cookie should expire
-
+
- Extracts one parameter from an array
+ Gets a collection enumerator on the cookie list.
- Containing the string array
- All but the first value
-
- string test1 = ExtractOne("system[user][extension][id]");
- string test2 = ExtractOne(test1);
- string test3 = ExtractOne(test2);
- // test1 = user[extension][id]
- // test2 = extension[id]
- // test3 = id
-
+ collection enumerator
-
- Resets all data contained by class
+
+
+ Remove all cookies
+
-
+
Returns an enumerator that iterates through the collection.
@@ -1040,2593 +1160,2516 @@
1
-
+
- Returns an enumerator that iterates through a collection.
+ Gets the count of cookies in the collection.
-
-
- An object that can be used to iterate through the collection.
-
- 2
-
+
- Form name as lower case
+ Gets the cookie of a given identifier (null if not existing).
-
+
- Get a form item.
+ cookie being sent back to the browser.
-
- Returns if item was not found.
+
-
+
- Small design by contract implementation.
+ cookie sent by the client/browser
+
-
+
- Check whether a parameter is empty.
+ Constructor.
- Parameter value
- Parameter name, or error description.
- value is empty.
+ cookie identifier
+ cookie content
+ id or content is null
+ id is empty
-
+
- Checks whether a parameter is null.
+ Gets the cookie HTML representation.
- Parameter value
- Parameter name, or error description.
- value is null.
+ cookie string
-
+
- Checks whether a parameter is null.
+ Gets the cookie identifier.
-
- Parameter value
- Parameter name, or error description.
- value is null.
-
+
- Contains all HTTP Methods (according to the HTTP 1.1 specification)
-
- See: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
-
+ Cookie value. Set to null to remove cookie.
-
+
- The DELETE method requests that the origin server delete the resource identified by the Request-URI.
+ Constructor.
-
-
- This method MAY be overridden by human intervention (or other means) on the origin server.
- The client cannot be guaranteed that the operation has been carried out, even if the status code
- returned from the origin server indicates that the action has been completed successfully.
-
-
- However, the server SHOULD NOT indicate success unless, at the time the response is given,
- it intends to delete the resource or move it to an inaccessible location.
-
-
- A successful response SHOULD be 200 (OK) if the response includes an entity describing the status,
- 202 (Accepted) if the action has not yet been enacted,
- or 204 (No Content) if the action has been enacted but the response does not include an entity.
-
-
- If the request passes through a cache and the Request-URI identifies one or more currently cached entities,
- those entries SHOULD be treated as stale. Responses to this method are not cacheable.
-
-
-
-
-
- The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI.
-
-
-
- If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the
- entity in the response and not the source text of the process, unless that text happens to be the output of the process.
-
-
- The semantics of the GET method change to a "conditional GET" if the request message includes an
- If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range header field.
- A conditional GET method requests that the entity be transferred only under the circumstances described
- by the conditional header field(s). The conditional GET method is intended to reduce unnecessary network
- usage by allowing cached entities to be refreshed without requiring multiple requests or transferring
- data already held by the client.
-
-
-
-
-
- The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response.
-
-
- The meta information contained in the HTTP headers in response to a HEAD request SHOULD be identical to the
- information sent in response to a GET request. This method can be used for obtaining meta information about
- the entity implied by the request without transferring the entity-body itself.
-
- This method is often used for testing hypertext links for validity, accessibility, and recent modification.
-
-
-
-
- The OPTIONS method represents a request for information about the communication options available on the request/response chain identified by the Request-URI.
-
-
- This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
-
-
-
-
- The POST method is used to request that the origin server accept the entity enclosed
- in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line.
-
-
- POST is designed to allow a uniform method to cover the following functions:
-
- -
- Annotation of existing resources;
-
-
- Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;
-
-
- Providing a block of data, such as the result of submitting a form, to a data-handling process;
-
-
- Extending a database through an append operation.
-
-
-
- If a resource has been created on the origin server, the response SHOULD be 201 (Created) and
- contain an entity which describes the status of the request and refers to the new resource, and a
- Location header (see section 14.30).
-
-
- The action performed by the POST method might not result in a resource that can be identified by a URI.
- In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on
- whether or not the response includes an entity that describes the result.
-
- Responses to this method are not cacheable, unless the response includes appropriate Cache-Control
- or Expires header fields. However, the 303 (See Other) response can be used to direct the user agent
- to retrieve a cacheable resource.
-
-
-
-
-
- The PUT method requests that the enclosed entity be stored under the supplied Request-URI.
-
-
-
- -
- If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a
- modified version of the one residing on the origin server.
-
-
- If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new
- resource by the requesting user agent, the origin server can create the resource with that URI.
-
-
- If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response.
-
-
- If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to
- indicate successful completion of the request.
-
-
- If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be
- given that reflects the nature of the problem.
-
-
-
- The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) headers that it does not
- understand or implement and MUST return a 501 (Not Implemented) response in such cases.
-
-
+ cookie identifier
+ cookie content
+ cookie expiration date. Use DateTime.MinValue for session cookie.
+ id or content is null
+ id is empty
-
+
- The TRACE method is used to invoke a remote, application-layer loop- back of the request message.
+ Create a new cookie
+ name identifying the cookie
+ cookie value
+ when the cookie expires. Setting DateTime.MinValue will delete the cookie when the session is closed.
+ Path to where the cookie is valid
+ Domain that the cookie is valid for.
-
+
- Contains all HTTP Methods (according to the HTTP 1.1 specification)
-
- See: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
-
+ Create a new cookie
+ Name and value will be used
+ when the cookie expires.
-
+
- The DELETE method requests that the origin server delete the resource identified by the Request-URI.
+ Gets the cookie HTML representation.
-
-
- This method MAY be overridden by human intervention (or other means) on the origin server.
- The client cannot be guaranteed that the operation has been carried out, even if the status code
- returned from the origin server indicates that the action has been completed successfully.
-
-
- However, the server SHOULD NOT indicate success unless, at the time the response is given,
- it intends to delete the resource or move it to an inaccessible location.
-
-
- A successful response SHOULD be 200 (OK) if the response includes an entity describing the status,
- 202 (Accepted) if the action has not yet been enacted,
- or 204 (No Content) if the action has been enacted but the response does not include an entity.
-
-
- If the request passes through a cache and the Request-URI identifies one or more currently cached entities,
- those entries SHOULD be treated as stale. Responses to this method are not cacheable.
-
-
+ cookie string
-
+
- The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI.
+ When the cookie expires.
+ DateTime.MinValue means that the cookie expires when the session do so.
-
-
- If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the
- entity in the response and not the source text of the process, unless that text happens to be the output of the process.
-
-
- The semantics of the GET method change to a "conditional GET" if the request message includes an
- If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range header field.
- A conditional GET method requests that the entity be transferred only under the circumstances described
- by the conditional header field(s). The conditional GET method is intended to reduce unnecessary network
- usage by allowing cached entities to be refreshed without requiring multiple requests or transferring
- data already held by the client.
-
-
-
+
- The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response.
+ Cookie is only valid under this path.
-
- The meta information contained in the HTTP headers in response to a HEAD request SHOULD be identical to the
- information sent in response to a GET request. This method can be used for obtaining meta information about
- the entity implied by the request without transferring the entity-body itself.
-
- This method is often used for testing hypertext links for validity, accessibility, and recent modification.
-
-
+
- The OPTIONS method represents a request for information about the communication options available on the request/response chain identified by the Request-URI.
+ Inversion of control interface.
-
- This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
-
-
+
- The POST method is used to request that the origin server accept the entity enclosed
- in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line.
+ Add a component instance
-
- POST is designed to allow a uniform method to cover the following functions:
-
- -
- Annotation of existing resources;
-
-
- Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;
-
-
- Providing a block of data, such as the result of submitting a form, to a data-handling process;
-
-
- Extending a database through an append operation.
-
-
-
- If a resource has been created on the origin server, the response SHOULD be 201 (Created) and
- contain an entity which describes the status of the request and refers to the new resource, and a
- Location header (see section 14.30).
-
-
- The action performed by the POST method might not result in a resource that can be identified by a URI.
- In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on
- whether or not the response includes an entity that describes the result.
-
- Responses to this method are not cacheable, unless the response includes appropriate Cache-Control
- or Expires header fields. However, the 303 (See Other) response can be used to direct the user agent
- to retrieve a cacheable resource.
-
-
+ Interface type
+ Instance to add
-
+
- The PUT method requests that the enclosed entity be stored under the supplied Request-URI.
+ Get a component.
+ Interface type
+ Component if registered, otherwise null.
-
- -
- If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a
- modified version of the one residing on the origin server.
-
-
- If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new
- resource by the requesting user agent, the origin server can create the resource with that URI.
-
-
- If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response.
-
-
- If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to
- indicate successful completion of the request.
-
-
- If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be
- given that reflects the nature of the problem.
-
-
-
- The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) headers that it does not
- understand or implement and MUST return a 501 (Not Implemented) response in such cases.
-
+ Component will get created if needed.
-
-
- The TRACE method is used to invoke a remote, application-layer loop- back of the request message.
-
-
-
-
- Priority for log entries
-
-
-
-
-
- Very detailed logs to be able to follow the flow of the program.
-
-
-
-
- Logs to help debug errors in the application
-
-
-
+
- Information to be able to keep track of state changes etc.
+ Checks if the specified component interface have been added.
+
+ true if found; otherwise false.
-
+
- Something did not go as we expected, but it's no problem.
+ Add a component.
+ Type being requested.
+ Type being created.
-
+
- Something that should not fail failed, but we can still keep
- on going.
+ Contains a listener that doesn't do anything with the connections.
-
+
- Something failed, and we cannot handle it properly.
+ Listen for regular HTTP connections
+ IP Address to accept connections on
+ TCP Port to listen on, default HTTP port is 80.
+ Factory used to create es.
+ address is null.
+ Port must be a positive number.
-
+
- Interface used to write to log files.
+ Initializes a new instance of the class.
+ IP Address to accept connections on
+ TCP Port to listen on, default HTTPS port is 443
+ Factory used to create es.
+ Certificate to use
-
+
- Write an entry to the log file.
+ Initializes a new instance of the class.
- object that is writing to the log
- importance of the log message
- the message
+ IP Address to accept connections on
+ TCP Port to listen on, default HTTPS port is 443
+ Factory used to create es.
+ Certificate to use
+ which HTTPS protocol to use, default is TLS.
-
-
- This class writes to the console. It colors the output depending on the logprio and includes a 3-level stacktrace (in debug mode)
-
-
+
+ Exception.
-
+
- The actual instance of this class.
+ Will try to accept connections one more time.
+ If any exceptions is thrown.
-
+
- Logwriters the specified source.
+ Can be used to create filtering of new connections.
- object that wrote the logentry.
- Importance of the log message
- The message.
+ Accepted socket
+ true if connection can be accepted; otherwise false.
-
+
- Get color for the specified logprio
+ Start listen for new connections
- prio for the log entry
- A for the prio
+ Number of connections that can stand in a queue to be accepted.
+ Listener have already been started.
-
+
- Default log writer, writes everything to null (nowhere).
+ Stop the listener
-
+
-
+
- The logging instance.
+ Gives you a change to receive log entries for all internals of the HTTP library.
+
+ You may not switch log writer after starting the listener.
+
-
+
- Writes everything to null
+ True if we should turn on trace logs.
- object that wrote the log entry.
- Importance of the log message
- The message.
-
+
- Inversion of control interface.
+ Catch exceptions not handled by the listener.
+
+ Exceptions will be thrown during debug mode if this event is not used,
+ exceptions will be printed to console and suppressed during release mode.
+
-
+
- Add a component instance
+ A request have been received from a .
- Interface type
- Instance to add
-
+
- Get a component.
+ New implementation of the HTTP listener.
- Interface type
- Component if registered, otherwise null.
- Component will get created if needed.
+ Use the Create methods to create a default listener.
-
+
- Checks if the specified component interface have been added.
+ Initializes a new instance of the class.
-
- true if found; otherwise false.
+ IP Address to accept connections on
+ TCP Port to listen on, default HTTP port is 80.
+ Factory used to create es.
+ address is null.
+ Port must be a positive number.
-
+
- Add a component.
+ Initializes a new instance of the class.
- Type being requested.
- Type being created.
+ The address.
+ The port.
+ The factory.
+ The certificate.
-
+
- Returns item either from a form or a query string (checks them in that order)
+ Initializes a new instance of the class.
+ The address.
+ The port.
+ The factory.
+ The certificate.
+ The protocol.
-
- Representation of a non-initialized HttpParam
-
-
- Initialises the class to hold a value either from a post request or a querystring request
-
-
+
- The add method is not availible for HttpParam
- since HttpParam checks both Request.Form and Request.QueryString
+ Creates a new instance with default factories.
- name identifying the value
- value to add
-
+ Address that the listener should accept connections on.
+ Port that listener should accept connections on.
+ Created HTTP listener.
-
+
- Checks whether the form or querystring has the specified value
+ Creates a new instance with default factories.
- Name, case sensitive
- true if found; otherwise false.
+ Address that the listener should accept connections on.
+ Port that listener should accept connections on.
+ Certificate to use
+ Created HTTP listener.
-
+
- Returns an enumerator that iterates through the collection.
+ Creates a new instance with default factories.
-
-
- A that can be used to iterate through the collection.
-
- 1
+ Address that the listener should accept connections on.
+ Port that listener should accept connections on.
+ Certificate to use
+ which HTTPS protocol to use, default is TLS.
+ Created HTTP listener.
-
+
- Returns an enumerator that iterates through a collection.
+ Can be used to create filtering of new connections.
-
+ Accepted socket
- An object that can be used to iterate through the collection.
+ true if connection can be accepted; otherwise false.
- 2
-
+
- Fetch an item from the form or querystring (in that order).
+ A client have been accepted, but not handled, by the listener.
-
- Item if found; otherwise HttpInputItem.EmptyLanguageNode
-
-
- Container for posted form data
-
-
- Instance to help mark a non-initialized form
-
-
- Initializes a form container with the specified name
-
+
- Makes a deep copy of the input
+ redirects from one URL to another.
- The input to copy
-
+
- Adds a file to the collection of posted files
+ Rules are used to perform operations before a request is being handled.
+ Rules can be used to create routing etc.
- The file to add
- If the file is already added
- If file is null
- If the instance is HttpForm.EmptyForm which cannot be modified
-
+
- Checks if the form contains a specified file
+ Process the incoming request.
- Field name of the file parameter
- True if the file exists
- If the instance is HttpForm.EmptyForm which cannot be modified
+ incoming HTTP request
+ outgoing HTTP response
+ true if response should be sent to the browser directly (no other rules or modules will be processed).
+
+ returning true means that no modules will get the request. Returning true is typically being done
+ for redirects.
+
+ If request or response is null.
-
+
- Retrieves a file held by by the form
+ Initializes a new instance of the class.
- The identifier of the file
- The requested file or null if the file was not found
- If name is null or empty
- If the instance is HttpForm.EmptyForm which cannot be modified
-
-
- Disposes all held HttpFile's and resets values
+ Absolute path (no server name)
+ Absolute path (no server name)
+
+ server.Add(new RedirectRule("/", "/user/index"));
+
-
+
- Retrieves the number of files added to the
+ Initializes a new instance of the class.
- 0 if no files are added
+ Absolute path (no server name)
+ Absolute path (no server name)
+ true if request should be redirected, false if the request URI should be replaced.
+
+ server.Add(new RedirectRule("/", "/user/index"));
+
-
+
- The object form class takes an object and creates form items for it.
+ Process the incoming request.
+ incoming HTTP request
+ outgoing HTTP response
+ true if response should be sent to the browser directly (no other rules or modules will be processed).
+
+ returning true means that no modules will get the request. Returning true is typically being done
+ for redirects.
+
-
+
- Initializes a new instance of the class.
+ Gets string to match request URI with.
-
- form name *and* id.
- action to do when form is posted.
-
+ Is compared to request.Uri.AbsolutePath
-
+
- Initializes a new instance of the class.
+ Gets where to redirect.
- form name *and* id.
- action to do when form is posted.
- object to get values from
-
+
- Initializes a new instance of the class.
+ Gets whether server should redirect client.
- form action.
- object to get values from.
+
+ false means that the rule will replace
+ the current request URI with the new one from this class.
+ true means that a redirect response is sent to the client.
+
-
+
- write out the FORM-tag.
+ Parses a HTTP request directly from a stream
- generated html code
-
+
- Writeout the form tag
+ Event driven parser used to parse incoming HTTP requests.
- form should be posted through ajax.
- generated html code
+
+ The parser supports partial messages and keeps the states between
+ each parsed buffer. It's therefore important that the parser gets
+ ed if a client disconnects.
+
-
+
- Generates a text box.
+ Parse partial or complete message.
-
-
- generated html code
+ buffer containing incoming bytes
+ where in buffer that parsing should start
+ number of bytes to parse
+ Unparsed bytes left in buffer.
+ BadRequestException.
-
+
- password box
+ Clear parser state.
-
-
- generated html code
-
+
- Hiddens the specified property name.
+ Current state in parser.
- Name of the property.
- The options.
- generated html code
-
+
- Labels the specified property name.
+ A request have been successfully parsed.
- property in object.
- caption
- generated html code
-
+
- Generate a checkbox
+ More body bytes have been received.
- property in object
- checkbox value
- additional html attributes.
- generated html code
-
+
- Write a html select tag
+ Request line have been received.
- object property.
- id column
- The title column.
- The options.
-
-
+
- Selects the specified property name.
+ A header have been received.
- Name of the property.
- The items.
- The id column.
- The title column.
- The options.
-
-
+
- Write a submit tag.
+ Gets or sets the log writer.
- button caption
- html submit tag
-
+
- html end form tag
+ Create a new request parser
- html
+ delegate receiving log entries.
-
+
- This provider is used to let us implement any type of form decoding we want without
- having to rewrite anything else in the server.
+ Add a number of bytes to the body
+ buffer containing more body bytes.
+ starting offset in buffer
+ number of bytes, from offset, to read.
+ offset to continue from.
-
+
-
+ Remove all state information for the request.
- Should contain boundary and type, as in: multipart/form-data; boundary=---------------------------230051238959
- Stream containing form data.
- Encoding used when decoding the stream
- if no parser was found.
- If stream is null or not readable.
- If stream contents cannot be decoded properly.
-
+
- Add a decoder.
+ Parse request line
-
-
+
+ If line is incorrect
+ Expects the following format: "Method SP Request-URI SP HTTP-Version CRLF"
-
+
- Number of added decoders.
+ We've parsed a new header.
+ Name in lower case
+ Value, unmodified.
+ If content length cannot be parsed.
-
+
- Use with care.
+ Parse a message
+ bytes to parse.
+ where in buffer that parsing should start
+ number of bytes to parse, starting on .
+ offset (where to start parsing next).
+ BadRequestException.
-
+
- Decoder used for unknown content types.
+ Gets or sets the log writer.
-
+
- We dont want to let the server to die due to exceptions thrown in worker threads.
- therefore we use this delegate to give you a change to handle uncaught exceptions.
+ Current state in parser.
- Class that the exception was thrown in.
- Exception
-
- Server will throw a InternalServerException in release version if you dont
- handle this delegate.
-
-
+
- Contains a connection to a browser/client.
+ A request have been successfully parsed.
-
- Remember to after you have hooked the event.
-
- TODO: Maybe this class should be broken up into HttpClientChannel and HttpClientContext?
-
+
- Initializes a new instance of the class.
+ More body bytes have been received.
- true if the connection is secured (SSL/TLS)
- client that connected.
- Stream used for communication
- Used to create a .
- Size of buffer to use when reading data. Must be at least 4096 bytes.
- If fails
- Stream must be writable and readable.
-
+
- Process incoming body bytes.
+ Request line have been received.
-
- Bytes
-
+
-
+ A header have been received.
-
-
-
+
- Start reading content.
+ Contains server side HTTP request information.
-
- Make sure to call base.Start() if you override this method.
-
-
+
- Clean up context.
-
-
- Make sure to call base.Cleanup() if you override the method.
-
+ Called during parsing of a .
+
+ Name of the header, should not be URL encoded
+ Value of the header, should not be URL encoded
+ If a header is incorrect.
-
+
- Disconnect from client
+ Add bytes to the body
- error to report in the event.
+ buffer to read bytes from
+ where to start read
+ number of bytes to read
+ Number of bytes actually read (same as length unless we got all body bytes).
+ If body is not writable
+ bytes is null.
+ offset is out of range.
-
+
- Send a response.
+ Clear everything in the request
- Either or
- HTTP status code
- reason for the status code.
- HTML body contents, can be null or empty.
- A content type to return the body as, i.e. 'text/html' or 'text/plain', defaults to 'text/html' if null or empty
- If is invalid.
-
+
- Send a response.
+ Decode body into a form.
- Either or
- HTTP status code
- reason for the status code.
+ A list with form decoders.
+ If body contents is not valid for the chosen decoder.
+ If body is still being transferred.
-
+
- Send a response.
+ Sets the cookies.
-
+ The cookies.
-
+
- send a whole buffer
+ Create a response object.
- buffer to send
-
+ Context for the connected client.
+ A new .
-
+
- Send data using the stream
+ Gets kind of types accepted by the client.
- Contains data to send
- Start position in buffer
- number of bytes to send
-
-
-
+
- This context have been cleaned, which means that it can be reused.
+ Gets or sets body stream.
-
+
- Context have been started (a new client have connected)
+ Gets whether the body is complete.
-
+
- Overload to specify own type.
+ Gets or sets kind of connection used for the session.
-
- Must be specified before the context is being used.
-
-
+
- Using SSL or other encryption method.
+ Gets or sets number of bytes in the body.
-
+
- Using SSL or other encryption method.
+ Gets cookies that was sent with the request.
-
+
- Specify which logger to use.
+ Gets form parameters.
-
+
- Gets or sets the network stream.
+ Gets headers sent by the client.
-
+
- Gets or sets IP address that the client connected from.
+ Gets or sets version of HTTP protocol that's used.
+
+ Probably or .
+
+
-
+
- Gets or sets port that the client connected from.
+ Gets whether the request was made by Ajax (Asynchronous JavaScript)
-
+
- The context have been disconnected.
+ Gets or sets requested method.
- Event can be used to clean up a context, or to reuse it.
+ Will always be in upper case.
+
-
+
- A request have been received in the context.
+ Gets parameter from or .
-
+
- Helpers to make XML handling easier
+ Gets variables sent in the query string
-
+
- Serializes object to XML.
+ Gets or sets requested URI.
- object to serialize.
- XML
+
+
+
+ Gets URI absolute path divided into parts.
+
+
+ // URI is: http://gauffin.com/code/tiny/
+ Console.WriteLine(request.UriParts[0]); // result: code
+ Console.WriteLine(request.UriParts[1]); // result: tiny
+
- Removes name spaces and adds indentation
+ If you're using controllers than the first part is controller name,
+ the second part is method name and the third part is Id property.
+
-
+
- Create an object from a XML string
+ Gets or sets path and query.
- Type of object
- XML string
- object
+
+
+ Are only used during request parsing. Cannot be set after "Host" header have been
+ added.
+
-
+
- Can handle application/x-www-form-urlencoded
+ PrototypeJS implementation of the javascript functions.
-
+
+ Purpose of this class is to create a javascript toolkit independent javascript helper.
- Stream containing the content
- Content type (with any additional info like boundry). Content type is always supplied in lower case
- Stream encoding
-
- A HTTP form, or null if content could not be parsed.
-
- If contents in the stream is not valid input data.
-
+
- Checks if the decoder can handle the mime type
+ Generates a list with JS options.
- Content type (with any additional info like boundry). Content type is always supplied in lower case.
- True if the decoder can parse the specified content type
+ StringBuilder that the options should be added to.
+ the javascript options. name, value pairs. each string value should be escaped by YOU!
+ true if we should start with a comma.
-
+
- Invoked when a client have been accepted by the
+ Removes any javascript parameters from an array of parameters
-
- Can be used to revoke incoming connections
-
+ The array of parameters to remove javascript params from
+ An array of html parameters
-
+
- Initializes a new instance of the class.
+ javascript action that should be added to the "onsubmit" event in the form tag.
- The socket.
+
+ All javascript option names should end with colon.
+
+
+ JSHelper.AjaxRequest("/user/show/1", "onsuccess:", "$('userInfo').update(result);");
+
+
-
+
- Client may not be handled.
+ Requests a url through ajax
+ url to fetch
+ optional options in format "key, value, key, value", used in JS request object.
+ a link tag
+ All javascript option names should end with colon.
+
+
+ JSHelper.AjaxRequest("/user/show/1", "onsuccess:", "$('userInfo').update(result);");
+
+
-
+
- Accepted socket.
+ Ajax requests that updates an element with
+ the fetched content
+ Url to fetch content from
+ element to update
+ optional options in format "key, value, key, value", used in JS updater object.
+ A link tag.
+ All javascript option names should end with colon.
+
+
+ JSHelper.AjaxUpdater("/user/show/1", "userInfo", "onsuccess:", "alert('Successful!');");
+
+
-
+
- Client should be revoked.
+ A link that pop ups a Dialog (overlay div)
+ url to contents of dialog
+ link title
+ A "a"-tag that popups a dialog when clicked
+ name/value of html attributes
+
+ WebHelper.DialogLink("/user/show/1", "show user", "onmouseover", "alert('booh!');");
+
-
+
- Arguments sent when a is cleared
+ Close a javascript dialog window/div.
+ javascript for closing a dialog.
+
-
+
- Instantiates the arguments for the event
+ Creates a new modal dialog window
- True if the session is cleared due to expiration
+ url to open in window.
+ window title (may not be supported by all js implementations)
+
+
-
+
- Returns true if the session is cleared due to expiration
+ Requests a url through ajax
+ url to fetch. Url is NOT enclosed in quotes by the implementation. You need to do that yourself.
+ optional options in format "key, value, key, value", used in JS request object. All keys should end with colon.
+ a link tag
+ onclick attribute is used by this method.
+
+
+ // plain text
+ JSHelper.AjaxRequest("'/user/show/1'");
+
+ // ajax request using this.href
+ string link = "<a href=\"/user/call/1\" onclick=\"" + JSHelper.AjaxRequest("this.href") + "/<call user</a>";
+
+
-
+
- Delegate for when a IHttpSession is cleared
+ Determins if a list of strings contains a specific value
- this is being cleared.
- Arguments for the clearing
+ options to check in
+ value to find
+ true if value was found
+ case insensitive
-
+
- Event arguments used when a new header have been parsed.
+ Ajax requests that updates an element with
+ the fetched content
+ URL to fetch. URL is NOT enclosed in quotes by the implementation. You need to do that yourself.
+ element to update
+ options in format "key, value, key, value". All keys should end with colon.
+ A link tag.
+
+
+ JSHelper.AjaxUpdater("'/user/show/1'", "user", "onsuccess:", "alert('hello');", "asynchronous:", "true");
+
+
-
+
- Initializes a new instance of the class.
+ A link that pop ups a Dialog (overlay div)
- Name of header.
- Header value.
+ URL to contents of dialog
+ link title
+ name, value, name, value
+
+ A "a"-tag that popups a dialog when clicked
+
+ Requires Control.Modal found here: http://livepipe.net/projects/control_modal/
+ And the following JavaScript (load it in application.js):
+
+ Event.observe(window, 'load',
+ function() {
+ document.getElementsByClassName('modal').each(function(link){ new Control.Modal(link); });
+ }
+ );
+
+
+
+ WebHelper.DialogLink("/user/show/1", "show user", "onmouseover", "alert('booh!');");
+
-
+
- Initializes a new instance of the class.
+ create a modal dialog (usually using DIVs)
+ url to fetch
+ dialog title
+ javascript/html attributes. javascript options ends with colon ':'.
+
-
+
- Gets or sets header name.
+ Close a javascript dialog window/div.
+ javascript for closing a dialog.
+
-
+
- Gets or sets header value.
+ javascript action that should be added to the "onsubmit" event in the form tag.
+ remember to encapsulate strings in ''
+
+ All javascript option names should end with colon.
+
+
+ JSHelper.AjaxRequest("/user/show/1", "onsuccess:", "$('userInfo').update(result);");
+
+
-
- Class to handle loading of resource files
-
-
+
- Initializes a new instance of the class.
+ Helpers making it easier to work with forms.
+
-
+
- Initializes a new instance of the class.
+ Used to let the website use different JavaScript libraries.
+ Default is
- logger.
-
+
- Loads resources from a namespace in the given assembly to an URI
+ Create a <form> tag.
- The URI to map the resources to
- The assembly in which the resources reside
- The namespace from which to load the resources
-
+ name of form
+ action to invoke on submit
+ form should be posted as Ajax
+ HTML code
+
- resourceLoader.LoadResources("/user/", typeof(User).Assembly, "MyLib.Models.User.Views");
+ // without options
+ WebHelper.FormStart("frmLogin", "/user/login", Request.IsAjax);
+
+ // with options
+ WebHelper.FormStart("frmLogin", "/user/login", Request.IsAjax, "style", "display:inline", "class", "greenForm");
- Will make the resource MyLib.Models.User.Views.list.Haml accessible via /user/list.haml or /user/list/
-
- The amount of loaded files, giving you the possibility of making sure the resources needed gets loaded
- If a resource has already been mapped to an uri
+
+ HTML attributes or JavaScript options.
+ Method will ALWAYS be POST.
+ options must consist of name, value, name, value
-
+
- Retrieves a stream for the specified resource path if loaded otherwise null
+ Creates a select list with the values in a collection.
- Path to the resource to retrieve a stream for
- A stream or null if the resource couldn't be found
+ Name of the SELECT-tag
+ collection used to generate options.
+ delegate used to return id and title from objects.
+ value that should be marked as selected.
+ First row should contain an empty value.
+ string containing a SELECT-tag.
+
-
+
- Fetch all files from the resource that matches the specified arguments.
+ Creates a select list with the values in a collection.
- The path to the resource to extract
-
- a list of files if found; or an empty array if no files are found.
-
- Search path must end with an asterisk for finding arbitrary files
+ Name of the SELECT-tag
+ Id of the SELECT-tag
+ collection used to generate options.
+ delegate used to return id and title from objects.
+ value that should be marked as selected.
+ First row should contain an empty value.
+ string containing a SELECT-tag.
+
+
+
+ // Class that is going to be used in a SELECT-tag.
+ public class User
+ {
+ private readonly string _realName;
+ private readonly int _id;
+ public User(int id, string realName)
+ {
+ _id = id;
+ _realName = realName;
+ }
+ public string RealName
+ {
+ get { return _realName; }
+ }
+
+ public int Id
+ {
+ get { return _id; }
+ }
+ }
+
+ // Using an inline delegate to generate the select list
+ public void UserInlineDelegate()
+ {
+ List<User> items = new List<User>();
+ items.Add(new User(1, "adam"));
+ items.Add(new User(2, "bertial"));
+ items.Add(new User(3, "david"));
+ string htmlSelect = Select("users", "users", items, delegate(object o, out object id, out object value)
+ {
+ User user = (User)o;
+ id = user.Id;
+ value = user.RealName;
+ }, 2, true);
+ }
+
+ // Using an method as delegate to generate the select list.
+ public void UseExternalDelegate()
+ {
+ List<User> items = new List<User>();
+ items.Add(new User(1, "adam"));
+ items.Add(new User(2, "bertial"));
+ items.Add(new User(3, "david"));
+ string htmlSelect = Select("users", "users", items, UserOptions, 1, true);
+ }
+
+ // delegate returning id and title
+ public static void UserOptions(object o, out object id, out object title)
+ {
+ User user = (User)o;
+ id = user.Id;
+ value = user.RealName;
+ }
+
+
+ name, id, collection or getIdTitle is null.
-
+
- Fetch all files from the resource that matches the specified arguments.
+ Creates a select list with the values in a collection.
- Where the file should reside.
- Files to check
-
- a list of files if found; or an empty array if no files are found.
-
+ Name of the SELECT-tag
+ Id of the SELECT-tag
+ collection used to generate options.
+ delegate used to return id and title from objects.
+ value that should be marked as selected.
+ First row should contain an empty value.
+ name, value collection of extra HTML attributes.
+ string containing a SELECT-tag.
+
+ name, id, collection or getIdTitle is null.
+ Invalid HTML attribute list.
-
+
- Returns whether or not the loader has an instance of the file requested
+ Generate a list of HTML options
- The name of the template/file
- True if the loader can provide the file
+ collection used to generate options.
+ delegate used to return id and title from objects.
+ value that should be marked as selected.
+ First row should contain an empty value.
+
+ collection or getIdTitle is null.
-
-
- redirects from one URL to another.
-
+
+ sb is null.
-
+
- Rules are used to perform operations before a request is being handled.
- Rules can be used to create routing etc.
+ Creates a check box.
+ element name
+ element value
+ determines if the check box is selected or not. This is done differently depending on the
+ type of variable. A boolean simply triggers checked or not, all other types are compared with "value" to determine if
+ the box is checked or not.
+ a list with additional attributes (name, value, name, value).
+ a generated radio button
-
+
- Process the incoming request.
+ Creates a check box.
- incoming HTTP request
- outgoing HTTP response
- true if response should be sent to the browser directly (no other rules or modules will be processed).
+ element name
+ element id
+ element value
+ determines if the check box is selected or not. This is done differently depending on the
+ type of variable. A boolean simply triggers checked or not, all other types are compared with "value" to determine if
+ the box is checked or not.
+ a list with additional attributes (name, value, name, value).
+ a generated radio button
- returning true means that no modules will get the request. Returning true is typically being done
- for redirects.
+ value in your business object. (check box will be selected if it matches the element value)
- If request or response is null.
-
-
-
- Initializes a new instance of the class.
-
- Absolute path (no server name)
- Absolute path (no server name)
-
- server.Add(new RedirectRule("/", "/user/index"));
-
-
+
- Initializes a new instance of the class.
+ Creates a check box.
- Absolute path (no server name)
- Absolute path (no server name)
- true if request should be redirected, false if the request URI should be replaced.
-
- server.Add(new RedirectRule("/", "/user/index"));
-
+ element name
+ element id
+ determines if the check box is selected or not. This is done differently depending on the
+ type of variable. A boolean simply triggers checked or not, all other types are compared with "value" to determine if
+ the box is checked or not.
+ a list with additional attributes (name, value, name, value).
+ a generated radio button
+ will set value to "1".
-
+
- Process the incoming request.
+ Creates a RadioButton.
- incoming HTTP request
- outgoing HTTP response
- true if response should be sent to the browser directly (no other rules or modules will be processed).
-
- returning true means that no modules will get the request. Returning true is typically being done
- for redirects.
-
+ element name
+ element value
+ determines if the radio button is selected or not. This is done differently depending on the
+ type of variable. A boolean simply triggers checked or not, all other types are compared with "value" to determine if
+ the box is checked or not.
+ a list with additional attributes (name, value, name, value).
+ a generated radio button
-
+
- Gets string to match request URI with.
+ Creates a RadioButton.
- Is compared to request.Uri.AbsolutePath
+ element name
+ element id
+ element value
+ determines if the radio button is selected or not. This is done differently depending on the
+ type of variable. A boolean simply triggers checked or not, all other types are compared with "value" to determine if
+ the box is checked or not.
+ a list with additional attributes (name, value, name, value).
+ a generated radio button
-
+
- Gets where to redirect.
+ form close tag
+
-
+
- Gets whether server should redirect client.
+ We dont want to let the server to die due to exceptions thrown in worker threads.
+ therefore we use this delegate to give you a change to handle uncaught exceptions.
+ Class that the exception was thrown in.
+ Exception
- false means that the rule will replace
- the current request URI with the new one from this class.
- true means that a redirect response is sent to the client.
+ Server will throw a InternalServerException in release version if you dont
+ handle this delegate.
-
+
- Used to queue incoming requests.
+ Implements HTTP Digest authentication. It's more secure than Basic auth since password is
+ encrypted with a "key" from the server.
+
+ Keep in mind that the password is encrypted with MD5. Use a combination of SSL and digest auth to be secure.
+
-
+
- Initializes a new instance of the class.
+ Authentication modules are used to implement different
+ kind of HTTP authentication.
- Called when a request should be processed.
-
+
- Used to process queued requests.
+ Tag used for authentication.
-
+
- Gets or sets maximum number of allowed simultaneous requests.
+ Initializes a new instance of the class.
+ Delegate used to provide information used during authentication.
+ Delegate used to determine if authentication is required (may be null).
-
+
- Gets or sets maximum number of requests queuing to be handled.
+ Initializes a new instance of the class.
+ Delegate used to provide information used during authentication.
-
+
- Specifies how many requests the HTTP server is currently processing.
+ Create a response that can be sent in the WWW-Authenticate header.
+ Realm that the user should authenticate in
+ Array with optional options.
+ A correct authentication request.
+ If realm is empty or null.
-
+
- Used two queue incoming requests to avoid
- thread starvation.
+ An authentication response have been received from the web browser.
+ Check if it's correct
+ Contents from the Authorization header
+ Realm that should be authenticated
+ GET/POST/PUT/DELETE etc.
+ options to specific implementations
+ Authentication object that is stored for the request. A user class or something like that.
+ if is invalid
+ If any of the parameters is empty or null.
-
+
- Method used to process a queued request
+ Used to invoke the authentication delegate that is used to lookup the user name/realm.
- Context that the request was received from.
- Request to process.
+ Realm (domain) that user want to authenticate in
+ User name
+ Password used for validation. Some implementations got password in clear text, they are then sent to client.
+ object that will be stored in the request to help you identify the user if authentication was successful.
+ true if authentication was successful
-
+
- Parses a HTTP request directly from a stream
+ Determines if authentication is required.
+ HTTP request from browser
+ true if user should be authenticated.
+ throw from your delegate if no more attempts are allowed.
+ If no more attempts are allowed
-
+
- Event driven parser used to parse incoming HTTP requests.
+ name used in HTTP request.
-
- The parser supports partial messages and keeps the states between
- each parsed buffer. It's therefore important that the parser gets
- ed if a client disconnects.
-
-
+
- Parse partial or complete message.
+ Initializes a new instance of the class.
- buffer containing incoming bytes
- where in buffer that parsing should start
- number of bytes to parse
- Unparsed bytes left in buffer.
- BadRequestException.
+ Delegate used to provide information used during authentication.
+ Delegate used to determine if authentication is required (may be null).
-
+
- Clear parser state.
+ Initializes a new instance of the class.
+ Delegate used to provide information used during authentication.
-
+
- Current state in parser.
+ Used by test classes to be able to use hardcoded values
-
+
- A request have been successfully parsed.
+ An authentication response have been received from the web browser.
+ Check if it's correct
+ Contents from the Authorization header
+ Realm that should be authenticated
+ GET/POST/PUT/DELETE etc.
+ First option: true if username/password is correct but not cnonce
+
+ Authentication object that is stored for the request. A user class or something like that.
+
+ if authenticationHeader is invalid
+ If any of the paramters is empty or null.
-
+
- More body bytes have been received.
+ Encrypts parameters into a Digest string
+ Realm that the user want to log into.
+ User logging in
+ Users password.
+ HTTP method.
+ Uri/domain that generated the login prompt.
+ Quality of Protection.
+ "Number used ONCE"
+ Hexadecimal request counter.
+ "Client Number used ONCE"
+ Digest encrypted string
-
+
- Request line have been received.
+
+ Md5 hex encoded "userName:realm:password", without the quotes.
+ Md5 hex encoded "method:uri", without the quotes
+ Quality of Protection
+ "Number used ONCE"
+ Hexadecimal request counter.
+ Client number used once
+
-
+
- A header have been received.
+ Create a response that can be sent in the WWW-Authenticate header.
+ Realm that the user should authenticate in
+ First options specifies if true if username/password is correct but not cnonce.
+ A correct auth request.
+ If realm is empty or null.
-
+
- Gets or sets the log writer.
+ Decodes authorization header value
+ header value
+ Encoding that the buffer is in
+ All headers and their values if successful; otherwise null
+
+ NameValueCollection header = DigestAuthentication.Decode("response=\"6629fae49393a05397450978507c4ef1\",\r\nc=00001", Encoding.ASCII);
+
+ Can handle lots of whitespaces and new lines without failing.
-
+
- Create a new request parser
+ Gets the current nonce.
- delegate receiving log entries.
+
-
+
- Add a number of bytes to the body
+ Gets the Md5 hash bin hex2.
- buffer containing more body bytes.
- starting offset in buffer
- number of bytes, from offset, to read.
- offset to continue from.
+ To be hashed.
+
-
+
- Remove all state information for the request.
+ determines if the nonce is valid or has expired.
+ nonce value (check wikipedia for info)
+ true if the nonce has not expired.
-
+
- Parse request line
+ name used in http request.
-
- If line is incorrect
- Expects the following format: "Method SP Request-URI SP HTTP-Version CRLF"
-
+
- We've parsed a new header.
+ Gets or sets whether the token supplied in is a
+ HA1 generated string.
- Name in lower case
- Value, unmodified.
- If content length cannot be parsed.
-
+
- Parse a message
+ Generic helper functions for HTTP
- bytes to parse.
- where in buffer that parsing should start
- number of bytes to parse, starting on .
- offset (where to start parsing next).
- BadRequestException.
-
+
- Gets or sets the log writer.
+ Version string for HTTP v1.0
-
+
- Current state in parser.
+ Version string for HTTP v1.1
-
+
- A request have been successfully parsed.
+ An empty URI
-
+
- More body bytes have been received.
+ Parses a query string.
+ Query string (URI encoded)
+ A object if successful; otherwise
+ queryString is null.
+ If string cannot be parsed.
-
+
- Request line have been received.
+ Delegate used to let authentication modules authenticate the user name and password.
+ Realm that the user want to authenticate in
+ User name specified by client
+ Can either be user password or implementation specific token.
+ object that will be stored in a session variable called if authentication was successful.
+ throw forbidden exception if too many attempts have been made.
+
+
+ Use to specify that the token is a HA1 token. (MD5 generated
+ string from realm, user name and password); Md5String(userName + ":" + realm + ":" + password);
+
+
-
+
- A header have been received.
+ Let's you decide on a system level if authentication is required.
+ HTTP request from client
+ true if user should be authenticated.
+ throw if no more attempts are allowed.
+ If no more attempts are allowed
-
+
- Response that is sent back to the web browser / client.
-
- A response can be sent if different ways. The easiest one is
- to just fill the Body stream with content, everything else
- will then be taken care of by the framework. The default content-type
- is text/html, you should change it if you send anything else.
-
- The second and slighty more complex way is to send the response
- as parts. Start with sending the header using the SendHeaders method and
- then you can send the body using SendBody method, but do not forget
- to set ContentType and ContentLength before doing so.
+ Arguments used when more body bytes have come.
-
- public void MyHandler(IHttpRequest request, IHttpResponse response)
- {
-
- }
-
-
+
- Add another header to the document.
+ Initializes a new instance of the class.
- Name of the header, case sensitive, use lower cases.
- Header values can span over multiple lines as long as each line starts with a white space. New line chars should be \r\n
- If headers already been sent.
- If value conditions have not been met.
- Adding any header will override the default ones and those specified by properties.
+ buffer that contains the received bytes.
+ offset in buffer where to start processing.
+ number of bytes from that should be parsed.
-
+
- Send headers and body to the browser.
+ Initializes a new instance of the class.
- If content have already been sent.
-
+
- Make sure that you have specified ContentLength and sent the headers first.
+ Gets or sets buffer that contains the received bytes.
-
- If headers have not been sent.
-
- offest of first byte to send
- number of bytes to send.
-
-
- This method can be used if you want to send body contents without caching them first. This
- is recommended for larger files to keep the memory usage low.
-
+
- Make sure that you have specified ContentLength and sent the headers first.
+ Gets or sets number of bytes from that should be parsed.
-
- If headers have not been sent.
-
-
-
- This method can be used if you want to send body contents without caching them first. This
- is recommended for larger files to keep the memory usage low.
-
+
- Send headers to the client.
+ Gets or sets offset in buffer where to start processing.
- If headers already been sent.
-
-
-
-
+
- Redirect client to somewhere else using the 302 status code.
+ Contains all HTTP Methods (according to the HTTP 1.1 specification)
+
+ See: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
+
- Destination of the redirect
- If headers already been sent.
- You can not do anything more with the request when a redirect have been done. This should be your last
- action.
-
+
- redirect to somewhere
+ The DELETE method requests that the origin server delete the resource identified by the Request-URI.
- where the redirect should go
- No body are allowed when doing redirects.
+
+ This method MAY be overridden by human intervention (or other means) on the origin server.
+ The client cannot be guaranteed that the operation has been carried out, even if the status code
+ returned from the origin server indicates that the action has been completed successfully.
+
+
+ However, the server SHOULD NOT indicate success unless, at the time the response is given,
+ it intends to delete the resource or move it to an inaccessible location.
+
+
+ A successful response SHOULD be 200 (OK) if the response includes an entity describing the status,
+ 202 (Accepted) if the action has not yet been enacted,
+ or 204 (No Content) if the action has been enacted but the response does not include an entity.
+
+
+ If the request passes through a cache and the Request-URI identifies one or more currently cached entities,
+ those entries SHOULD be treated as stale. Responses to this method are not cacheable.
+
-
+
- The body stream is used to cache the body contents
- before sending everything to the client. It's the simplest
- way to serve documents.
+ The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI.
+
+
+ If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the
+ entity in the response and not the source text of the process, unless that text happens to be the output of the process.
+
+
+ The semantics of the GET method change to a "conditional GET" if the request message includes an
+ If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range header field.
+ A conditional GET method requests that the entity be transferred only under the circumstances described
+ by the conditional header field(s). The conditional GET method is intended to reduce unnecessary network
+ usage by allowing cached entities to be refreshed without requiring multiple requests or transferring
+ data already held by the client.
+
+
-
+
- Defines the version of the HTTP Response for applications where it's required
- for this to be forced.
+ The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response.
+
+ The meta information contained in the HTTP headers in response to a HEAD request SHOULD be identical to the
+ information sent in response to a GET request. This method can be used for obtaining meta information about
+ the entity implied by the request without transferring the entity-body itself.
+
+ This method is often used for testing hypertext links for validity, accessibility, and recent modification.
+
-
+
- The chunked encoding modifies the body of a message in order to
- transfer it as a series of chunks, each with its own size indicator,
- followed by an OPTIONAL trailer containing entity-header fields. This
- allows dynamically produced content to be transferred along with the
- information necessary for the recipient to verify that it has
- received the full message.
+ The OPTIONS method represents a request for information about the communication options available on the request/response chain identified by the Request-URI.
+
+ This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
+
-
+
- Kind of connection
+ The POST method is used to request that the origin server accept the entity enclosed
+ in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line.
+
+ POST is designed to allow a uniform method to cover the following functions:
+
+ -
+ Annotation of existing resources;
+
-
+ Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;
+
-
+ Providing a block of data, such as the result of submitting a form, to a data-handling process;
+
-
+ Extending a database through an append operation.
+
+
+
+ If a resource has been created on the origin server, the response SHOULD be 201 (Created) and
+ contain an entity which describes the status of the request and refers to the new resource, and a
+ Location header (see section 14.30).
+
+
+ The action performed by the POST method might not result in a resource that can be identified by a URI.
+ In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on
+ whether or not the response includes an entity that describes the result.
+
+ Responses to this method are not cacheable, unless the response includes appropriate Cache-Control
+ or Expires header fields. However, the 303 (See Other) response can be used to direct the user agent
+ to retrieve a cacheable resource.
+
+
-
+
- Encoding to use when sending stuff to the client.
+ The PUT method requests that the enclosed entity be stored under the supplied Request-URI.
- Default is UTF8
+
+
+ -
+ If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a
+ modified version of the one residing on the origin server.
+
-
+ If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new
+ resource by the requesting user agent, the origin server can create the resource with that URI.
+
-
+ If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response.
+
-
+ If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to
+ indicate successful completion of the request.
+
-
+ If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be
+ given that reflects the nature of the problem.
+
+
+
+ The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) headers that it does not
+ understand or implement and MUST return a 501 (Not Implemented) response in such cases.
+
+
-
+
- Number of seconds to keep connection alive
+ The TRACE method is used to invoke a remote, application-layer loop- back of the request message.
- Only used if Connection property is set to ConnectionType.KeepAlive
-
+
- Status code that is sent to the client.
+ Contains all HTTP Methods (according to the HTTP 1.1 specification)
+
+ See: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
+
- Default is HttpStatusCode.Ok
-
+
- Information about why a specific status code was used.
+ The DELETE method requests that the origin server delete the resource identified by the Request-URI.
+
+
+ This method MAY be overridden by human intervention (or other means) on the origin server.
+ The client cannot be guaranteed that the operation has been carried out, even if the status code
+ returned from the origin server indicates that the action has been completed successfully.
+
+
+ However, the server SHOULD NOT indicate success unless, at the time the response is given,
+ it intends to delete the resource or move it to an inaccessible location.
+
+
+ A successful response SHOULD be 200 (OK) if the response includes an entity describing the status,
+ 202 (Accepted) if the action has not yet been enacted,
+ or 204 (No Content) if the action has been enacted but the response does not include an entity.
+
+
+ If the request passes through a cache and the Request-URI identifies one or more currently cached entities,
+ those entries SHOULD be treated as stale. Responses to this method are not cacheable.
+
+
-
+
- Size of the body. MUST be specified before sending the header,
- unless property Chunked is set to true.
+ The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI.
+
+
+ If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the
+ entity in the response and not the source text of the process, unless that text happens to be the output of the process.
+
+
+ The semantics of the GET method change to a "conditional GET" if the request message includes an
+ If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range header field.
+ A conditional GET method requests that the entity be transferred only under the circumstances described
+ by the conditional header field(s). The conditional GET method is intended to reduce unnecessary network
+ usage by allowing cached entities to be refreshed without requiring multiple requests or transferring
+ data already held by the client.
+
+
-
+
- Kind of content in the body
+ The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response.
- Default is text/html
+
+ The meta information contained in the HTTP headers in response to a HEAD request SHOULD be identical to the
+ information sent in response to a GET request. This method can be used for obtaining meta information about
+ the entity implied by the request without transferring the entity-body itself.
+
+ This method is often used for testing hypertext links for validity, accessibility, and recent modification.
+
-
+
- Headers have been sent to the client-
+ The OPTIONS method represents a request for information about the communication options available on the request/response chain identified by the Request-URI.
- You can not send any additional headers if they have already been sent.
+
+ This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
+
-
+
- The whole response have been sent.
+ The POST method is used to request that the origin server accept the entity enclosed
+ in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line.
+
+ POST is designed to allow a uniform method to cover the following functions:
+
+ -
+ Annotation of existing resources;
+
-
+ Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;
+
-
+ Providing a block of data, such as the result of submitting a form, to a data-handling process;
+
-
+ Extending a database through an append operation.
+
+
+
+ If a resource has been created on the origin server, the response SHOULD be 201 (Created) and
+ contain an entity which describes the status of the request and refers to the new resource, and a
+ Location header (see section 14.30).
+
+
+ The action performed by the POST method might not result in a resource that can be identified by a URI.
+ In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on
+ whether or not the response includes an entity that describes the result.
+
+ Responses to this method are not cacheable, unless the response includes appropriate Cache-Control
+ or Expires header fields. However, the 303 (See Other) response can be used to direct the user agent
+ to retrieve a cacheable resource.
+
+
-
+
- Cookies that should be created/changed.
+ The PUT method requests that the enclosed entity be stored under the supplied Request-URI.
+
+
+ -
+ If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a
+ modified version of the one residing on the origin server.
+
-
+ If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new
+ resource by the requesting user agent, the origin server can create the resource with that URI.
+
-
+ If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response.
+
-
+ If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to
+ indicate successful completion of the request.
+
-
+ If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be
+ given that reflects the nature of the problem.
+
+
+
+ The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) headers that it does not
+ understand or implement and MUST return a 501 (Not Implemented) response in such cases.
+
+
-
+
- Type of HTTP connection
+ The TRACE method is used to invoke a remote, application-layer loop- back of the request message.
-
+
- Connection is closed after each request-response
+ Used to create and reuse contexts.
-
+
- Connection is kept alive for X seconds (unless another request have been made)
+ Used to create es.
-
+
- Response that is sent back to the web browser / client.
+ Creates a that handles a connected client.
-
-
- A response can be sent if different ways. The easiest one is
- to just fill the Body stream with content, everything else
- will then be taken care of by the framework. The default content-type
- is text/html, you should change it if you send anything else.
-
- The second and slightly more complex way is to send the response
- as parts. Start with sending the header using the SendHeaders method and
- then you can send the body using SendBody method, but do not forget
- to set and before doing so.
-
-
-
-
- // Example using response body.
- class MyModule : HttpModule
- {
- public override bool Process(IHttpRequest request, IHttpResponse response, IHttpSession session)
- {
- StreamWriter writer = new StreamWriter(response.Body);
- writer.WriteLine("Hello dear World!");
- writer.Flush();
-
- // return true to tell webserver that we've handled the url
- return true;
- }
- }
-
-
- todo: add two examples, using SendHeaders/SendBody and just the Body stream.
+ Client socket (accepted by the ).
+ A creates .
-
+
- Initializes a new instance of the class.
+ Create a secure .
- Client that send the .
- Contains information of what the client want to receive.
- cannot be empty.
+ Client socket (accepted by the ).
+ HTTPS certificate to use.
+ Kind of HTTPS protocol. Usually TLS or SSL.
+ A created .
-
+
- Initializes a new instance of the class.
+ A request have been received from one of the contexts.
- Client that send the .
- Version of HTTP protocol that the client uses.
- Type of HTTP connection used.
-
+
- Add another header to the document.
+ Initializes a new instance of the class.
- Name of the header, case sensitive, use lower cases.
- Header values can span over multiple lines as long as each line starts with a white space. New line chars should be \r\n
- If headers already been sent.
- If value conditions have not been met.
- Adding any header will override the default ones and those specified by properties.
+ The writer.
+ Amount of bytes to read from the incoming socket stream.
+ Used to create a request parser.
-
+
- Send headers and body to the browser.
+ Create a new context.
- If content have already been sent.
+ true if socket is running HTTPS.
+ Client that connected
+ Network/SSL stream.
+ A context.
-
+
- Make sure that you have specified and sent the headers first.
+ Create a new context.
-
- If headers have not been sent.
-
- offset of first byte to send
- number of bytes to send.
-
-
- This method can be used if you want to send body contents without caching them first. This
- is recommended for larger files to keep the memory usage low.
+ true if HTTPS is used.
+ Remote client
+ Network stream, uses .
+ A new context (always).
-
+
- Make sure that you have specified and sent the headers first.
+ Create a secure .
-
- If headers have not been sent.
-
-
-
- This method can be used if you want to send body contents without caching them first. This
- is recommended for larger files to keep the memory usage low.
+ Client socket (accepted by the ).
+ HTTPS certificate to use.
+ Kind of HTTPS protocol. Usually TLS or SSL.
+
+ A created .
+
-
+
- Send headers to the client.
+ Creates a that handles a connected client.
- If headers already been sent.
-
-
-
+ Client socket (accepted by the ).
+
+ A creates .
+
-
+
- Redirect client to somewhere else using the 302 status code.
+ True if detailed trace logs should be written.
- Destination of the redirect
- If headers already been sent.
- You can not do anything more with the request when a redirect have been done. This should be your last
- action.
-
+
- redirect to somewhere
+ A request have been received from one of the contexts.
- where the redirect should go
-
- No body are allowed when doing redirects.
-
-
+
- The body stream is used to cache the body contents
- before sending everything to the client. It's the simplest
- way to serve documents.
+ Custom network stream to mark sockets as reusable when disposing the stream.
-
+
- The chunked encoding modifies the body of a message in order to
- transfer it as a series of chunks, each with its own size indicator,
- followed by an OPTIONAL trailer containing entity-header fields. This
- allows dynamically produced content to be transferred along with the
- information necessary for the recipient to verify that it has
- received the full message.
+ Creates a new instance of the class for the specified .
+
+ The that the will use to send and receive data.
+
+
+ The parameter is null.
+
+
+ The parameter is not connected.
+ -or-
+ The property of the parameter is not .
+ -or-
+ The parameter is in a nonblocking state.
+
-
+
- Defines the version of the HTTP Response for applications where it's required
- for this to be forced.
+ Initializes a new instance of the class for the specified with the specified ownership.
+
+ The that the will use to send and receive data.
+
+
+ Set to true to indicate that the will take ownership of the ; otherwise, false.
+
+
+ The parameter is null.
+
+
+ The parameter is not connected.
+ -or-
+ the value of the property of the parameter is not .
+ -or-
+ the parameter is in a nonblocking state.
+
-
+
- Kind of connection
+ Creates a new instance of the class for the specified with the specified access rights.
+
+ The that the will use to send and receive data.
+
+
+ A bitwise combination of the values that specify the type of access given to the over the provided .
+
+
+ The parameter is null.
+
+
+ The parameter is not connected.
+ -or-
+ the property of the parameter is not .
+ -or-
+ the parameter is in a nonblocking state.
+
-
+
- Encoding to use when sending stuff to the client.
+ Creates a new instance of the class for the specified with the specified access rights and the specified ownership.
- Default is UTF8
+
+ The that the will use to send and receive data.
+
+
+ A bitwise combination of the values that specifies the type of access given to the over the provided .
+
+
+ Set to true to indicate that the will take ownership of the ; otherwise, false.
+
+
+ The parameter is null.
+
+
+ The parameter is not connected.
+ -or-
+ The property of the parameter is not .
+ -or-
+ The parameter is in a nonblocking state.
+
-
+
- Number of seconds to keep connection alive
+ Closes the current stream and releases any resources (such as sockets and file handles) associated with the current stream.
- Only used if Connection property is set to .
-
+
- Status code that is sent to the client.
+ Releases the unmanaged resources used by the and optionally releases the managed resources.
- Default is
+ true to release both managed and unmanaged resources; false to release only unmanaged resources.
-
+
- Information about why a specific status code was used.
+ Invoked when a client have been accepted by the
+
+ Can be used to revoke incoming connections
+
-
+
- Size of the body. MUST be specified before sending the header,
- unless property Chunked is set to true.
+ Initializes a new instance of the class.
+ The socket.
-
+
- Kind of content in the body
+ Client may not be handled.
- Default type is "text/html"
-
+
- Headers have been sent to the client-
+ Accepted socket.
- You can not send any additional headers if they have already been sent.
-
+
- The whole response have been sent.
+ Client should be revoked.
-
+