Skip to main content

Your connection is not private

Almost all web developers facing this issue without knowing the path of the problem.

When we try to access the secure web sites, I mean https, Google Chrome browser says "Your connection is not private". What we do usually, just click ADVANCED link
and Proceed to (unsafe). 


At times, we will not see Proceed to (unsafe) link after clicking ADVANCED. We see the below screen instead which says "You cannot visit right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later." 


If you see the above screen don't get upset.

Type chrome://net-internals/#hsts in address bar and hit Enter.

In Delete domain enter your domain name and do delete. You can verify you domain's status in Query domain.


Once you done the specified steps then you can see Proceed to (unsafe) link. 

Enjoy!
Labels:

Comments

Post a Comment

Popular posts from this blog

What's Virtual DOM?

There’s no big difference between the regular DOM and the virtual DOM. It’s better to think of the virtual DOM as React’s local and simplified copy of the HTML DOM. It allows React to do its computations within this abstract world and skip the real DOM operations, often slow and browser-specific. Real DOM operations are really really expensive. The Virtual DOM is an abstraction of the HTML DOM. It is lightweight and detached from the browser-specific implementation details.  One thing you should remember that the DOM itself was already an abstraction. So, Virtual DOM is an abstraction of an abstraction. :)
Post a Comment
Read more

ASP.NET Dynamic Compilation

In ASP.NET Web Applications, When we request a page it must parse and compile the code of Web Application into one or more assemblies. When the code is compiled, it's translated into a language independent and CPU independent code, that's MSIL code. When we create an ASP.NET page, actually creating the source code for a .NET class. We are creating a new instance of the System.Web.UI.Page class.The entire contents of an ASP.NET page, including all script and HTML content, are compiled into a .NET class. When request an ASP.NET page, ASP.NET Framework checks for a .NET class that corresponds to that page. If a corresponding class does not exist, the Framework automatically compiles the page into a new class and stores the compiled class (the assembly) in the Temporary ASP.NET Files folder. The Temporary ASP.NET files folder located at : \WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files The next time anyone requests the same page in the future, the page is not co...
Post a Comment
Read more