The security rules when running from file:// is different than http://
Set up your debug config to deploy to a server and debug from there and find
out what requests are being made. Lots of people manage to lock "localhost"
into their configuration. I'm not sure how.
I know what requests are being made. It might be even correct that it's not working for me and that is not scarring me - as long as we can make a sense of error messages it's fine. But what my frustration is that these messages are so controversial it's impossible to understand what exactly is wrong. Like I said, first it tries localhost which in case of running from a test computer means exactly what? Then I see the secure connection failing, but I am not using any secure connection for my testing.
Localhost is usually mapped to the computer it is running on. Normally,
folks don't ever want to see a request to localhost unless they are deployed
on localhost. I would be trying to find out why localhost is still being