httpcontext

问题 foreach (string key in HttpContext.Current.Request.Form.AllKeys) { string value = HttpContext.Current.Request.Form[key]; } What is the .net core version of the above code? Seems like .net core took out AllKeys and replaced it with Keys instead. I tried to convert the above code to the .net core way, but it throws an invalid operation exception. HttpContext.Request.Form = 'HttpContext.Request.Form' threw an exception of type 'System.InvalidOperationException' Converted code: foreach (string

来源： https://stackoverflow.com/questions/51996907/httpcontext-features-vs-httpcontext-items-in-asp-net-core

来源： https://stackoverflow.com/questions/51996907/httpcontext-features-vs-httpcontext-items-in-asp-net-core

问题 I'm building an asp.net core web application on framework 2.2 and hosting on an azure app service on a linux app service plan. Inside my application I inspect HttpRequest.Scheme. Running locally this returns https if I make a request using https. Running on azure it returns http . It appears Azure App Services is terminating the SSL connection and proxying to my app. Is there a way to configure Azure App Services so the https request makes it to my application unmodified? Or at least

问题 I created a Blazor client app and and within this app I have a number of authorization policies with custom requirements and handlers. One of them checks the ID requested in the URL and checks whether the logged in user can view this resource. For example, through the client, the user navigates to https://localhost/resource/1f28e41c-bc75-44d6-9eef-d46b66b649c7 which is a resource on my API. I’m using the following code to see the request path: var httpContext = _httpContextAccessor

问题 I created a Blazor client app and and within this app I have a number of authorization policies with custom requirements and handlers. One of them checks the ID requested in the URL and checks whether the logged in user can view this resource. For example, through the client, the user navigates to https://localhost/resource/1f28e41c-bc75-44d6-9eef-d46b66b649c7 which is a resource on my API. I’m using the following code to see the request path: var httpContext = _httpContextAccessor

问题 I created a Blazor client app and and within this app I have a number of authorization policies with custom requirements and handlers. One of them checks the ID requested in the URL and checks whether the logged in user can view this resource. For example, through the client, the user navigates to https://localhost/resource/1f28e41c-bc75-44d6-9eef-d46b66b649c7 which is a resource on my API. I’m using the following code to see the request path: var httpContext = _httpContextAccessor

问题 I am a beginner with HangFire and looking forward to using HangFire to call some actions in my web application monthly. But these actions require HttpContext. Then my question is: Is there any way to add (or create) a httpcontext in HangFire project? I tried to google but no suitable answer. Thanks for your help! I found a short discussion. Sad to see the answer is "no way". Update: Ref https://discuss.hangfire.io/t/passing-site-url-to-hangfire-recurrent-jobs/2641 回答1: I have a similar

问题 I've implemented a custom User Store for ASP.NET Identity by following the example set here. That all works fine, except for this: I need access to data about the currently logged in user in my user store. Normally, you'd access that by accessing HttpContext.Current.User Now, once auser has logged in, if he user then goes to the Manage controller (e.g. to try and change his/her password), when ASP.NET identity looks up the user again by calling CustomUserManager.FindByIdAsync(string userId)

问题 I've implemented a custom User Store for ASP.NET Identity by following the example set here. That all works fine, except for this: I need access to data about the currently logged in user in my user store. Normally, you'd access that by accessing HttpContext.Current.User Now, once auser has logged in, if he user then goes to the Manage controller (e.g. to try and change his/her password), when ASP.NET identity looks up the user again by calling CustomUserManager.FindByIdAsync(string userId)