Having a different internet browser makes handy for people whose job is to make sure any web service or application, and their behavior, would not fail before and after making any changes, or upgrade.
In our definition, it is that it would not fail regardless of methods, not the geeky ones and without harm of course, applied to access, in a regular way, a resource designed and made available to the public.
We think that premise, which is to "make sure it will work, somehow a little better", characteristic of our work @𝖎𝖈𝖑𝖆𝖘𝖘𝖊𝖉, is true to any technology designed for use mainstream but which this post is toned or using such example, specifically.
Do you know what causes a browser to process a web service or application like this in the image?
In our definition, it is that it would not fail regardless of methods, not the geeky ones and without harm of course, applied to access, in a regular way, a resource designed and made available to the public.
We think that premise, which is to "make sure it will work, somehow a little better", characteristic of our work @𝖎𝖈𝖑𝖆𝖘𝖘𝖊𝖉, is true to any technology designed for use mainstream but which this post is toned or using such example, specifically.
Do you know what causes a browser to process a web service or application like this in the image?
We would see it is due to an HSTS, primarily, not being processed or some bug prevented to load by, in here we have, Microsoft Edge Dev browser where a notice is produced. Then it could be that, with other browsers, this is not at all a problem and the service is working fine.
The web, as many of technology people are aware, has become a link to many related services. A single domain name, at first glance, may not appear to run many differentiated web services or applications but in reality it may have composed unique functions to complete the entirety of single web operation. In the case of e-commerce, it may contain services offered independently including payments, banking, inventory, supply chain, customer service, etcetera.
Going back. If we focused on the problem, what may have caused the problem? We would first check on the HSTS, different from HyperText Transfer Protocol Secure (HTTPS), itself. Turning off or removing it to check further, would it enable the service or application to load up? If not, what else may have been causing it?
We cannot also say, browsers doesn't support HSTS so it's better not to use for now. Same attitude with new internet security technologies, their application is not entertained until some time. When news have began to spread a probability of risk discovered specific to a certain application, if not that very popular practice we have so embraced.
How fast until you can, or when are you going to stop investigating, make amends you possibly can and conclude that something is wrong and being able to, point out precisely the problem without doubt? This makes one to narrow down the defect but it doesn't mean the goal to have the HSTS has already been resolved. Not yet, it is going to have a fresh start, but at least the quest to understand and run such service is near.
What would you do if you're certain that everything has been done according to available specifications and they should be working?
Comments