FormsAuthentication.SetAuthCookie(tbUsername.Text, true); bool x = User.Identity.IsAuthenticated; //true string y = User.Identity.Name; //”” The problem you have is at this point you’re only setting the authentication cookie, the IPrincipal that gets created inside the forms authentication module will not happen until there is a new request – so at that point the HttpContext.User is in a … Read more
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
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
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
Add the following to Blazor.Web.App.Startup.cs: services.AddHttpContextAccessor(); You also need this in <component-name>.cshtml @using Microsoft.AspNetCore.Http @inject IHttpContextAccessor httpContextAccessor Note: At the time when this answer was written, accessing the HttpContext was done as described above. Since then, Blazor has been under rapid development, and has fundamentally changed. It is definitely deprecated the usage described above, but … Read more
HttpContext.Current gets the current context by Thread (I looked into the implementation directly). It would be more correct to say that HttpContext is applied to a thread; or a thread “enters” the HttpContext. Using HttpContext.Current inside of async Task is not possible, because it can run on another Thread. Not at all; the default behavior … Read more
No, from MSDN on HttpContext.Current: “Gets or sets the HttpContext object for the current HTTP request.” In other words it is an HttpContext object, not a Page. You can get to the Page object via HttpContext using: Page page = HttpContext.Current.Handler as Page; if (page != null) { // Use page instance. }
I needed the same information for my IIS6 hosted WCF application and I found that this worked for me: string apPath = System.Web.Hosting.HostingEnvironment.ApplicationPhysicalPath; As always, YMMV.
I struggled with this problem the past few days. I suggest reading Scott Guthrie’s blog post Recipe: Enabling Windows Authentication within an Intranet ASP.NET Web application For me the problem was that although I had Windows Authentication enabled in IIS and I had <authentication mode=”Windows” /> in the <system.web> section of web.config, I was not … Read more
It means that IIS is free to use more than one thread to handle a single request, although not in parallel. Basically, IIS tries to perform I/O operations asynchronously, thus freeing the calling thread for the duration of the operation. That thread is returned to the pool and can be used to handle other requests … Read more