I have an ASP.NET web app. It has a CMS web application which I want to run on IIS(through Visual Studio). It’s .csproj file lists the project URL as https://localhost:27251/.
I am using HttpClient.PostAsync to call a REST web service (Unified Endpoint Management, but I doubt that is relevant) on a remote (internal LAN) server. The call is throwing an exception as follows: 10/15/2020 5:05:25 AM An error occurred while sending the request. 10/15/2020 5:05:25 AM at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() 10/15/2020 5:05:25 … Read more
In ,net core 2.1, I want to redirect from http to https.
First of all, I use .net core 2.1 to develop a single page application(angular 5). Following the link
https://www.hanselman.com/blog/DevelopingLocallyWithASPNETCoreUnderHTTPSSSLAndSelfSignedCerts.aspx
I am hosting on Azure and have it configured to only allow https. The backend is running ASP .NET Core in a Linux container. The webserver (Kestrel) is running without https enabled. I’ve configured Azure TLS/SSL settings to force https, so when users connect from the public internet, they have to use https. I have a cert that is signed by a cert authority and it’s configured in the Azure App Service -> TLS/SSL -> Bindings settings.
I have an issue with a C# PayTrace Gateway. The below code was working fine until yesterday when I believe they turned off SSL3 due to the Poodle Exploit. When running the code below we got the following message. The remote server has forcefully closed the connection. After doing some research on the problem we determined that because our IIS Server 7.5 was configured to still use SSL3, C# defaulted to SSL3, which PayTrace would forcibly close the connection. We then removed SSL3 from the server. Which then lead to the following error:
My customer has informed my of issues with their SSL and Internet Explorer. They said they get trust issues when accessing the URL.
How do I go about using HTTPS for some of the pages in my ASP.NET MVC based site?
Because of compliance reasons we have to switch off the support of some ciphers and SSL2 on our webservers. This is not really a problem, but we would also like to inform them, after their successful login into the website, that we suggest switching on TLS 1.2 in their browser in case they are not already connecting to the server with TLS 1.2. So the question I have is:
I read that a page which runs under an https connection cannot share an InProc Session (based on cookies) with another page (or the same for that matter) running under regular http. My site is running on Server 2003, IIS 6 and .Net 2.0.