HomeGroupsTalkZeitgeist
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.
  • LibraryThing
  • Book discussions
  • Your LibraryThing
  • Join to start using.

LibraryThing adds SSL

New features

Join LibraryThing to post.

This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.

2brightcopy
Feb 11, 2014, 4:13pm Top

That's a rather &mdashing move!

(Serious version: your html entities got munged.)

3lorannen
Feb 11, 2014, 4:28pm Top

>2 brightcopy: Yeah, sorry about that. All fixed now.

4samwilson.id.au
Feb 11, 2014, 7:56pm Top

This is good news.

My session was mungled however: I was being sent in 301/302 redirect circles from the HTTP to HTTPS URLs until I cleared all LT cookies and logged in again. All working now.

5suitable1
Feb 11, 2014, 8:11pm Top

munged?

6timspalding
Feb 11, 2014, 9:02pm Top

I like it. It's in between munged and bungled.

7samwilson.id.au
Feb 11, 2014, 9:48pm Top

Hehe, it's a slightly mungled word I think... :)

I'm afraid I'm not able to reproduce the looping I was getting before, Tim.

I suspect it was just a cached 301 for https://www.librarything.com/home and so was going to http://www.librarything.com/home, which then promptly 302'd it back to where it came from. Clearing FF's cache fixed it.

I'd thought it was something to do with the Firefox plugin HTTPS Everywhere that I had installed, but removing it didn't help. (On which topic, here's the ruleset that that add-on uses to redirect people: https://www.eff.org/https-everywhere/atlas/domains/librarything.com.html )

8prosfilaes
Feb 11, 2014, 11:25pm Top

#7: (On which topic, here's the ruleset that that add-on uses to redirect people: https://www.eff.org/https-everywhere/atlas/domains/librarything.com.html )

I was going to leave a note in their bug tracker, but I don't have a clue where to start trying to use that thing.

9samwilson.id.au
Feb 11, 2014, 11:40pm Top

I raised a related bug this morning: https://trac.torproject.org/projects/tor/ticket/10892

You can log in as a guest there with the username and password from this page: https://www.eff.org/https-everywhere/development

:)

10aqeeliz
Feb 12, 2014, 12:53am Top

I think the looping might be because of HTTPS Everywhere + previous LT Cookie/cache. I was getting the same thing on Firefox, but disabling the rule for LibraryThing, and clearing LT's cookie + FF Cache, fixed the issue.

11jjmcgaffey
Apr 5, 2014, 2:55am Top

Oddity - I'm not sure it's related to this, but it might be. On the ReadaThing wiki page, most of the profile entries in the timeline are http; a couple are https. The posters _might_ have done it intentionally - it's two members, and their entries are https every time they show up. Don't know, it's just weird.

12siddartha
Apr 17, 2014, 3:56pm Top

Better late than never. I hope it won't take much to have the whole site on https.

13CIELVIU
Oct 21, 2015, 1:09pm Top

I am trying to get SSL enabled for search widgets (/ltsw/) My secure page which is hosting the widget displays the search box but the results of a query appear unsecure. See an example here: https://ciel.viu.ca/teaching-learning-pedagogy/new-or-fairly-new-teaching/centre...

Group: New features

45,200 messages

This group does not accept members.

About

This topic is not marked as primarily about any work, author or other topic.

Touchstones

No touchstones

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 134,113,198 books! | Top bar: Always visible