allow Midori to connect to unsecure http:// sites
Could you allow Midori to connect to non-secure sites after a proper warning like "Accept Risk and Proceed" similar to what Epiphany does for instance ... there are still a lot of web servers that do not use https:// ... this would be very useful on Raspberry Pi . Thank you
What version are you running?
using apt install midori on raspbian Pi 3B +, I get midori 7.0 Copyright 2007-2018 Christian Dywan.
On Sat, May 31, 2025 at 4:43 PM Andy Valencia @.***> wrote:
vandys left a comment (midori-browser/core#474) https://github.com/midori-browser/core/issues/474#issuecomment-2925709659
What version are you running?
— Reply to this email directly, view it on GitHub https://github.com/midori-browser/core/issues/474#issuecomment-2925709659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC764ZWYRHCTVAXQ5RYXKKD3BIIATAVCNFSM6AAAAAB6KHO3E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRVG4YDSNRVHE . You are receiving this because you authored the thread.Message ID: @.***>
exactly : 7.0-2.1
On Sat, May 31, 2025 at 4:58 PM jeanrocco jr @.***> wrote:
using apt install midori on raspbian Pi 3B +, I get midori 7.0 Copyright 2007-2018 Christian Dywan.
On Sat, May 31, 2025 at 4:43 PM Andy Valencia @.***> wrote:
vandys left a comment (midori-browser/core#474) https://github.com/midori-browser/core/issues/474#issuecomment-2925709659
What version are you running?
— Reply to this email directly, view it on GitHub https://github.com/midori-browser/core/issues/474#issuecomment-2925709659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC764ZWYRHCTVAXQ5RYXKKD3BIIATAVCNFSM6AAAAAB6KHO3E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRVG4YDSNRVHE . You are receiving this because you authored the thread.Message ID: @.***>
The CHANGELOG for that flavor of Midori puts that back at late 2018. It subsequently had 8.0 and 9.0 major versions. I can confirm that the top of trunk of this lineage of Midori did SSL just fine. Not sure if you're up for compiling your own browser? It's not terribly hard to do. (I forked it for my own purposes as dev here has ceased.)
Ok thank's a lot, I will try to compile it but i read there were some changes for arm architectures. Have a good day .
Le sam. 31 mai 2025, 17 h 12, Andy Valencia @.***> a écrit :
vandys left a comment (midori-browser/core#474) https://github.com/midori-browser/core/issues/474#issuecomment-2925737649
The CHANGELOG for that flavor of Midori puts that back at late 2018. It subsequently had 8.0 and 9.0 major versions. I can confirm that the top of trunk of this lineage of Midori did SSL just fine. Not sure if you're up for compiling your own browser? It's not terribly hard to do. (I forked it for my own purposes as dev here has ceased.)
— Reply to this email directly, view it on GitHub https://github.com/midori-browser/core/issues/474#issuecomment-2925737649, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC764ZSNCRCW2T5PRXXRHTL3BILNBAVCNFSM6AAAAAB6KHO3E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRVG4ZTONRUHE . You are receiving this because you authored the thread.Message ID: @.***>
I'm pretty sure I built for armhf back in the day, and currently maintain arm64 along with amd64 and i486 (I no longer have an armhf device with anything like a modern Xorg). Ping me if you run into anything, maybe I'll remember what I did.
Thank's again.
Le sam. 31 mai 2025, 17 h 20, Andy Valencia @.***> a écrit :
vandys left a comment (midori-browser/core#474) https://github.com/midori-browser/core/issues/474#issuecomment-2925751837
I'm pretty sure I built for armhf back in the day, and currently maintain arm64 along with amd64 and i486 (I no longer have an armhf device with anything like a modern Xorg). Ping me if you run into anything, maybe I'll remember what I did.
— Reply to this email directly, view it on GitHub https://github.com/midori-browser/core/issues/474#issuecomment-2925751837, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC764ZV55FCYKPC6NNYHUPD3BIMKXAVCNFSM6AAAAAB6KHO3E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRVG42TCOBTG4 . You are receiving this because you authored the thread.Message ID: @.***>
One more thought... what is the error? If you're running a very old Raspbian, it may just be that your cert roots are all out of date. Just a thought.
Hello Andy,
cat os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye
so it is fairly new. I was trying to use Midori on my Raspberry Pi 3 B+ to browse a UISP powerbeam AC gen 2 antenna system (192.168.1.22) which uses a non-secure http access. Midori complained about the connection's bad TLS certificate and does not provide an unsecure bypass like most browsers do. Anyways, I figured out a workaround using on my MacbookPro something like "ssh -L8443:192.168.1.22:443 @.***" which firefox browser detects as an unsecure connection and ask me if I accept the risk and connects anyway ... I hope you can follow this very unclear explanation, but it works fine and I don't need to use Midori on the Pi. The point here is that Midori does not propose a bypass to connect to an unsecure "http:" site, other than that it works very well and is a nice tool.
Thank's
I understand. I'm glad you found a workaround--I'll probably add this on my own fork at some point.
The CHANGELOG for that flavor of Midori puts that back at late 2018. It subsequently had 8.0 and 9.0 major versions. I can confirm that the top of trunk of this lineage of Midori did SSL just fine. Not sure if you're up for compiling your own browser? It's not terribly hard to do. (I forked it for my own purposes as dev here has ceased.)
At Astian, we have taken on responsibility for maintaining Midori, and the new version is now based on Gecko and remains just as lightweight and powerful. We recommend that you migrate. https://astian.org/midori-browser, https://github.com/goastian/midori-desktop.