If you have access to the HttpContext, you can get the Local/Remote IpAddress from the Connection property like so: var remote = this.HttpContext.Connection.RemoteIpAddress; var local = this.HttpContext.Connection.LocalIpAddress;
You can get access to HttpContext.Current by enabling AspNetCompatibility, preferably via configuration: <configuration> <system.serviceModel> <serviceHostingEnvironment aspNetCompatibilityEnabled=”true”/> </system.serviceModel> </configuration> That in turn allows you to get access to the current user: HttpContext.Current.User – which is what you’re after, right? You can even enforce AspNetCompatibility by decorating your service class with an additional attribute: [AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Required)] … Read more
You can get the endpoint currently targeted and the Uri for it by doing: OperationContext.Current.RequestContext.RequestMessage.Headers.To which I think is the same thing as: OperationContext.Current.IncomingMessageHeaders.To This is a System.Uri object, and I believe you can just get the OriginalString or PathAndQuery, or whatever parts you want from it.
Use HttpContext.Current.Request.HttpMethod. See: http://msdn.microsoft.com/en-us/library/system.web.httprequest.httpmethod.aspx
Your question is asking a few things but I think item #1 is the answer you’re looking for. Is it fine to use Context.Items for caching on a per request basis? Yes. If in process, per request, per machine in the web farm is your criteria then Context.Items gives you that. Is Context.Items difficult to … Read more
The simplest way is to copy it to a MemoryStream – then call ToArray if you need to. If you’re using .NET 4, that’s really easy: MemoryStream ms = new MemoryStream(); curContext.Request.InputStream.CopyTo(ms); // If you need it… byte[] data = ms.ToArray(); EDIT: If you’re not using .NET 4, you can create your own implementation of … Read more
Make sure you set your application name in web.config <errorLog type=”Elmah.SqlErrorLog, Elmah” connectionStringName=”nibWeb” applicationName=”Nib.Services” /> and then ErrorLog.GetDefault(null).Log(new Error(error)); will work
As long as your web.config settings are correct, async/await works perfectly well with HttpContext.Current. I recommend setting httpRuntime targetFramework to 4.5 to remove all “quirks mode” behavior. Once that is done, plain async/await will work perfectly well. You’ll only run into problems if you’re doing work on another thread or if your await code is … Read more
Try prefixing it with System.Web. If I try System.Web.HttpContext.Current, then Current is there, but if I try HttpContext.Current, then it doesn’t recognize ‘Current’. I do have System.Web in my using statements, but I still seem to be required to specify it in order to get access to ‘Current’. @Chris’ answer points and explains the underlying … Read more
Note: This has been fixed in .Net Core 2.0. I’m not sure what is the status of the fix for .Net Framework. Calbertoferreira’s answer has some useful information, but the conclusion is mostly wrong. To create an archive, you don’t need seek, but you do need to be able to read the Position. According to … Read more