randomsnark
Aha, thanks! I guess that concludes this thread, as I don’t really expect to get a dev chiming in explaining why.
It’s not my preferred way of handling it but I don’t have the energy to make a fuss. I guess if I click a link that needs to be http, I’ll copy it to a browser, and if I post one I’ll remind others to do the same. Probably won’t come up often enough to care about.
At least you’ve satisfied my curiosity as to what was going on 😀
Edit: I was repeatedly told while trying to post this comment that the request timeout had expired. When the error stopped appearing, I had posted 4 copies of this message. I have deleted them but I apologize if they still spam your inbox as [deleted] or something.
Thanks for looking into this thoroughly, and for correctly noting what’s causing the situation with my specific example.
I contacted Two9A about his weird configuration before I made my original post, but have yet to get a reply from them. The specific example of xkcdsw is a separate issue unrelated to jerboa.
My main question was what is causing http links opened on lemmy through jerboa to redirect to https links - whether that is being done by the app or the instance or what. If it is the intended behavior of the jerboa app, I’m curious as to why it doesn’t leave the protocol up to the commenter.
Did you click the links before telling me that’s not how it works though? Other people are reporting the same result. I also get the same result on both my phone and desktop. Seems like two clicks would be less trouble than finding sources to back up a condescending and inaccurate response.
Here is some information supporting the fact that URLs can work that way (although the two links you quoted but did not click on from my original post already demonstrate that): https://superuser.com/questions/792202/different-website-at-https-then-at-http
Edit: bear in mind that to reproduce the behavior, you might need to type the http into your browser manually if you are using jerboa.
