Page 1 of 1

Web browser hell

Posted: Sun Jan 29, 2023 12:28 pm
by RGV250
Hi,
Not exactly a Flowcode issue but it is hampering my webserver progress, also it might end up an issue for the Flowcode webserver component.
I had been OK simulating a program that uses the webserver component but now (probably after a Firefox automatic upgrade) I can no longer do anything. I am assuming this will be an issue if I try to deploy it to the Pi as well.
The issue is that Firefox (and now Chrome) have decided to add "S" to the HTTP and so it does not find the Index.html file where it used to work OK. I could understand this if it was external but this is just on my PC, I really don't need saving from myself.
I have tried to switch this off in Firefox but even with the settings off it still refuses to work so a pretty poor show from the developes at Firefox.
Is there a browser that does not try to protect me from myself or is there a workaround?

Regards,
Bob

Re: Web browser hell

Posted: Sun Jan 29, 2023 12:33 pm
by kersing
Once this rewrite happened Firefox will continue to ‘recall’ the secure URL. The only work-around I’ve found is to stop Firefox, restart and use a ‘private’ session with the right URL (so no https)

Re: Web browser hell

Posted: Sun Jan 29, 2023 4:46 pm
by RGV250
Hi Kersing,
I did try that and got the same thing, I even cleared the cache which has not helped.

Bob

Re: Web browser hell

Posted: Sun Jan 29, 2023 9:41 pm
by RGV250
Hi,
I have got somewhere but not sure if I am on the right track for a permanent solution.
I think the issue occurs if the browser does not find the index.html file or at least before it times out. If this happens I think it then tries HTTPS and after that it remembers that setting and there does not seem to be any way out.
I changed the adress in the simulation and it is working for the time being. Not sure what will happen when I get to the real hardware.

Bob

Re: Web browser hell

Posted: Sun Jan 29, 2023 10:13 pm
by chipfryer27
Hi

With regards to Firefox, to be fair the developers openly say that they will implement security features asap even if the rest of the web is playing catch up. I've probably got an old copy of Mosaic bundled with CompuServe on a disk if you need it :)

I've been following your posts with interest. Very helpful.

Regards

Re: Web browser hell

Posted: Mon Jan 30, 2023 8:17 am
by RGV250
Hi ChipFryer,
Thanks for your reply, I am not sure an old version of Mosaic would be the right way to go. I do not know a lot about web stuff but I am learning, I got a book on html and then found it has all changed with html5 and CSS is thrown into the mix.
I think I have this under control for simulation at least but am not sure how it will go with the real hardware. I think that should be OK but the issue is going to be if I need to get access from outside my home network.

Bob

Re: Web browser hell

Posted: Mon Jan 30, 2023 10:22 am
by BenR
RGV250 wrote:
Sun Jan 29, 2023 9:41 pm
Hi,
I have got somewhere but not sure if I am on the right track for a permanent solution.
I think the issue occurs if the browser does not find the index.html file or at least before it times out. If this happens I think it then tries HTTPS and after that it remembers that setting and there does not seem to be any way out.
I changed the adress in the simulation and it is working for the time being. Not sure what will happen when I get to the real hardware.

Bob
This is my experience too, if you type in an address and there is a page there to serve it will work but if nothing there then it will jump from http to https and then not work even when the page is available. Just something to be aware of.

Re: Web browser hell

Posted: Mon Jan 30, 2023 12:41 pm
by RGV250
OK, I think I know what has been happening, I might be wrong, hopefully Ben can confirm this.
Even though I have an index.html file entering 192.168.1.65/index.html or 192.168.1.110/index.html does not find the file so it then adds the https and screws everything up.
192.168.1.65 is the address of the laptop where the index file is and 192.168.1.110 is the address in the flowcode file for simulation.
If I run the simulation first and then put 1922.168.1.110/index.html in the browser all works as it should.
I am now very careful to start the simulation up first and to close the browser window down before I stop the simulation.
This has been working all day with no issues so I hope it helps someone.
I now have a demo which can be simulated and has data being updated with no refresh of the screen by putting a frame in a page.
If anyone is interested please let me know and I will post it, I will do anyway later on when it is a bit more tidied up but that may be quite a bit later on.

Regards,
Bob

Re: Web browser hell

Posted: Mon Jan 30, 2023 12:50 pm
by chipfryer27
Hi Bob

I'd be interested but I'm in no real hurry as it's a back burner project at the moment. Whenever you get time would be fine for me.

Regards