Melanie 162dfd8a38 Merge branch 'avination-current' into careminster

2013-06-11 21:03:02 +01:00

..

Interfaces

Add method to remove JsonRpc Handlers from the server

2013-03-03 09:40:44 -05:00

Properties

Deleted all AssemblyFileVersion directives

2013-02-19 17:14:55 -08:00

BaseHTTPHandler.cs

…

BaseHttpServer.cs

Merge branch 'master' into careminster

2013-06-11 01:03:15 +01:00

BaseRequestHandler.cs

…

BaseStreamHandler.cs

…

BinaryStreamHandler.cs

…

GenericHTTPMethod.cs

…

JsonRPCMethod.cs

Add additional return status

2013-01-23 08:14:21 -05:00

JsonRpcResponse.cs

Add Json-Rpc 2.0 To Registered Handlers

2013-01-15 10:04:16 -05:00

LLSDMethod.cs

…

LLSDMethodString.cs

…

OSHttpHandler.cs

…

OSHttpHttpHandler.cs

…

OSHttpRequest.cs

…

OSHttpRequestPump.cs

…

OSHttpRequestQueue.cs

…

OSHttpResponse.cs

…

OSHttpServer.cs

…

OSHttpStatusCodes.cs

…

OSHttpXmlRpcHandler.cs

…

PollServiceEventArgs.cs

Supply proper type information for the various types of requests

2013-06-07 23:55:03 +01:00

PollServiceHttpRequest.cs

…

PollServiceRequestManager.cs

Merge branch 'avination-current' into careminster

2013-06-11 21:03:02 +01:00

RestDeserialiseHandler.cs

…

RestHTTPHandler.cs

…

RestMethod.cs

…

RestObjectPoster.cs

Revert "Added request.Proxy=null everywhere, as discussed in http://stackoverflow.com/questions/2519655/httpwebrequest-is-extremely-slow."

2012-09-30 07:48:03 -07:00

RestObjectPosterResponse.cs

Revert "Added request.Proxy=null everywhere, as discussed in http://stackoverflow.com/questions/2519655/httpwebrequest-is-extremely-slow."

2012-09-30 07:48:03 -07:00

RestSessionService.cs

Make sure we dispose of WebResponse, StreamReader and Stream in various places where we were not already.

2013-02-27 00:21:02 +00:00

RestStreamHandler.cs

…

WebsocketServerHandler.cs

* Add a Max Payload size property to the Websocket Server Handler. If you would like to restrict the maximum packet size, (and therefore protect against Memory DOSing) then you should set this. I defaulted it to 40MB. This means that in theory, a malicious user could connect and send a packet that claims that the payload is up to 40 mb (even if it doesn't actually turn out to be 40mb. More testing needs to be done on it where the packets are maliciously malformed.

2013-03-05 00:04:09 -05:00

XmlRpcMethod.cs

…