Join LibraryThing to post.
I was answering a post and wanted to add a link. I searched for circulation and found a link to http://blog.librarything.com/main/2015/02/new-feature-lending-a-k-a-circulation/
That worked fine, but when I copied the link into my post and tried to follow it, I get big security warnings and can't get to the page whether I leave it as http or change it to https.
The bug being that search should return https links, right?
ETA: I've tried to reproduce what you did but I'm getting https links. How did you get the above link?
No, the bug is probably the certificate warning I get when I go to the https version of that link... And if you are on the https version of LT, and follow that link, it leads you to the https version.
The certificate comes from *.webfaction.com and because that is not blog.librarything.com it complains (rightly so). (NET::ERR_CERT_COMMON_NAME_INVALID)
I searched for 'circulation', went to Wiki/Help and chose 'Lending'. That page is https://wiki.librarything.com/index.php/Lending
There is a link on the word 'Circulation' which took me to
As I said above, that link works fine, although I do think that we should get https links from LT.
My link here works fine. My link in the other thread (http://www.librarything.com/topic/61093#6789869) also seems to work now if I change it back to http. With https I get the security warning.
I understood from what Tim said here: http://www.librarything.com/topic/304284#6777575 that https should be prefered, partly to avoid getting security warnings, but LT is sending me to http pages a lot. Often, but not always, I get warnings in the URL line that the page is insecure. Doesn't really bother me much, but this time I ended up with a nonfunctional link. There were a few different warning pages before it settled on the one I get now, and I was certainly getting it with both prefixes earlier.
I'm pretty sure this is not a bug, but a matter of us needing to make the LT blog available on https (it's only active on http at the moment).
>5 lorannen: Why wouldn't that be considered a bug, since it causes those annoying warnings.
>6 jjwilson61: The issue with >1 MarthaJeanne: is that the link posted isn't actually the URL it's displaying there. On examination, that link is missing the "http://" (or "https://") part of the URL entirely, and starts just at blog.librarything.com...
If you're on https and viewing Talk, it will automatically substitute in https:// (which doesn't work). If you're on http:// it'll substitute in http:// and it works fine. I've raised the issue with developers, but am not sure what the solution is going to be yet. It's expected behavior, ergo, not a bug, but worth looking at, in any case.
This topic is part of LibraryThing's in-talk bug tracking.
Join or watch Bug Collectors to get "Bug Tracking" under "The World" in Talk all the time.
Category: Miscellaneous pages
Assigned to all
Reported by MarthaJeanne
Apr 8, 2:44am
49 days since last change
Reported. MarthaJeanne (Apr 8, 2:44am)
This topic is not marked as primarily about any work, author or other topic.