Ok, maybe this may be petty, but why do so many sites require that 'www' before the names? I have wasted lot sof time trying to navigate to sites by just their domain name, only to find out that I need the 'www'. What do I mean? Both of these should work:
But then why would some develop a site that doesn't work like that. For example (with apologies to Brent Rector):
UPDATE: I spelled it wrong, but now that so many RSS readers have it, I won’t change the title ;) It’s spelled Thawte, not Thwate, sorry for the confusion.
I browsed to AgiliTrain (my training company) and noticed that the SSL Cert was failing. Not a good thing. But it wasn’t expired, it couldn’t find the Intermediate Certificates that the issuer requires (I am using Thwate certs). I am not sure why this happens. Unfortunately my old GoDaddy certs didn’t need Intermediate Certificates. My next certs won’t either because it has caused me a lot of wasted time and energy. Much more than I saved going with the cheap Thwate certs.
|Using Visual Studio Code for ASP.NET Core Projects (new)|
|Implementing and Securing an API with ASP.NET Core (new)|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||126.96.36.199||Runtime Framework||.NETCoreApp,Version=v2.0|
|App Path||D:\home\site\wwwroot\||Runtime Version||.NET Core 4.6.00001.0|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|