Open an-awful-person opened 10 years ago
The box directing all domains to itself by design. The webserver however, has no https support compiled in to save memory so that's why the second request fails. Changing it to use plain http would work fine.
The tricky thing is that some browsers seem to autocorrect it to https when u used it before. When connected to the WiFi box access point you can go to https://draw.doodle3d.com and it will say "Unable to connect", then you can correct it to http://draw.doodle3d.com and you will get the Doodle3D webinterface (no autocorrection) (probably because it couldn't find a website) But when you're online and use https://draw.doodle3d.com it will give a "This Connection is Untrusted" warning (so it does find something) and then you can't go to http://draw.doodle3d.com anymore because it will keep auto correcting http to https. It will do this untill you remove your browser settings (not sure which part matters). Depending on your browser and browser addons it might automatically go to https when you go to draw.doodle3.com. It seems to happen in:
Seeing more browsers pushing https (which is great) what can we do? Could we disable https on draw.doodle3d.com specificly? How much space would it cost to add https support?
Chrome recognizes every adress except draw.doodle3d.com as doodle3d I am using chrome on my laptop and the browser recognizes every adress i typ as the doodle3d application except for the draw.doodle3d.com adress which it should recognize. Also notice how everything doesn't include the http except for draw.doodle3d.com.