Subtle changes, bugs and feedback

Posted on
Page
of 312
  • The logo turns black for 3 days after a cyclist fatality on London's roads.

  • I was hoping it was a subtle forum change, and not that, poor fella :(

  • I think I may have just fixed it (the images not loading thing).

    I think it was because I was using SPDY on sslcache.se.

    Anyhow... is it still happening? Accessing a heavy image page that you haven't accessed recently should test it.

    Still happening for me - images load a teeny bit (the first 10% or so), the rest stays grey for about a minute and the browser says 'transferring data sslcache.se', and then after a minute the grey box disappears and i just get a link to the image, that isn't clickable or selectable.

    I changed https://www.lfgss...... to http://www.lfgss.... and the images worked immediately. But unless I manually do that each time, the images don't work. :(

  • I've just tested again... on dial-up!

    And it works fine.

    Latest Chrome, latest Firefox, both tested on Windows... on dial-up and also on broadband.

    Works for me on OSX now too.

  • Still happening for me - images load a teeny bit (the first 10% or so), the rest stays grey for about a minute and the browser says 'transferring data sslcache.se', and then after a minute the grey box disappears and i just get a link to the image, that isn't clickable or selectable.

    I changed https://www.lfgss...... to http://www.lfgss.... and the images worked immediately. But unless I manually do that each time, the images don't work. :(

    What is your setup?

    I had some success reproducing the problem by replicating what other people are using. As far as I can now tell, it's solved. But if you can help me reproduce your environment I'll test that too.

    About the only thing I can't test is the connection itself.

    Oh, and one thing: If you've left your browsers open for days on end... could you close it fully so that it forgets that we were using SPDY.

  • me too!

    Mac Os X - 10.7.4
    Firefox 15.0
    4gb
    Sky broadband

    This is the setup. But I do often leave the browser open for days, and having just restarted it, things appear to be working :)

  • Sigh of relief... I thought I'd have to go buy a Mac this morning.

    Yeah, browsers tend to remember that a site was available on SPDY and continue to try and access things that way.

    So after I disabled SPDY, and thus solved the issue (I believe), it needed people to fully close their browsers.

    In theory this means that the browser will re-discover SPDY support when it then connects to the site again.

  • Ha glad you didnt have to buy a mac, they are bastards. Everything is back to it's good old self now so whatever you did, fixed it. Thanks!

  • all seems good here in mac+safari land too
    Thanks

  • OK, some of us are working... lfgss.com just got SPDY.

    So did sslcache.se

    No, that add-on doesn't load anything at all. It just looks at the underlying protocol being used and toggles an image based on it.

    It's just an indicator. It's not like it does anything more than just "if SPDY then green else grey".

    It just shows you that SPDY is in fact being used. Otherwise you'd have no indication at all.

    Was there any genuine and noticeable speed benefit? Thinking of tests like this: http://www.guypo.com/technical/not-as-spdy-as-you-thought/

  • I was basically serving the SSL version of the site from only 2 domains.

    Trusted content came from lfgss.com
    Untrusted content came from sslcache.se

    Because of the way in which SPDY works, effectively optimizing per domain, there were fractional speed improvements as a result of my only using 2 domains. There would have been little to no benefit if I wasn't reducing the number of domains contant came from.

    I effectively proxied ALL third party content (mostly images) through https://sslcache.se and SPDY was enabled on that domain.

    However, there is a weird bug going on. The bug didn't affect lfgss.com but did affect sslcache.se .

    I'm not sure yet the root cause, but it seems that when SPDY was enabled for the domain that wasn't serving the page itself, that requests in the browser would queue normally, and then one of them would block. At which point, the browser would wait and eventually timeout and abort the connections.

    The servers were fine, this was the browser aborting the connections. And it only happened when SPDY was used to serve assets and the assets were not on the same domain as the page.

    LFGSS without SPDY, sslcache.se without SPDY = works.
    LFGSS with SPDY, sslcache.se without SPDY = works.
    LFGSS without SPDY, sslcache.se with SPDY = does not work.
    LFGSS with SPDY, sslcache.se with SPDY = does not work.

    That said, as this really impacted people for a week and the implementation is identical on both LFGSS and sslcache.se, I was left feeling uncertain about SPDY and thinking that the nginx implementation may have some bugs in it still (it is only in beta). Hence, it's disabled on LFGSS too now.

  • By the way, sslcache.se is a node.js server running on Heroku.

    Pretty nice setup that they have.

  • Can you serve without SSL if the referrer is Google?
    Or if the referrer is anything other than LFGSS?

    That would be every single page being forced to be non-SSL then.

    Referrer information isn't supplied when you use SSL.

    To be precise (for BQ's benefit, as I know VB knows this), with HTTPS, SSL negotiation happens before the HTTP traffic begins and thus before any headers are sent. Fucks up a number of things (e.g. name-based virtual hosting). HTTP 1.1 did introduce a mechanism for starting a connection in plain text and upgrading to TLS, which would address most of those problems; sadly, there is fuck-all browser support for it.

  • not loving the inpost advertising for specific words. I know its your forum and you can do what you want with it but it does suck a bit...

  • not loving the inpost advertising for specific words. I know its your forum and you can do what you want with it but it does suck a bit...

    Woah.

    LFGSS has no such advertising.

    We do rewrite some content to:
    1) Embed videos and things like YouTube or Vimeo when linked
    2) Embed routes and maps when linked
    3) Fetching Amazon item photos when linked
    4) Convert some links to affiliate ones that fund the community, when linked

    But all of those are based on not changing the content posted in any substantial way at all.

    If you have adverts appearing that involves popups, keywords highlighted, and things like that... that's not something I've added and I would be very keen to identify it and then go ballistic at the company that inserted it.

    If you could you point me to an example, it would be much appreciated.

  • FWIW one of the PMs at my work was complaining that I'd broken some website of ours by adding links into the content that shouldn't have been there. They turned out to have been inserted into her browser by either a rogue Firefox addon or a virus of some kind.

    Punkture, you should run a malware scan on your machine to make sure it's clean.

  • ok, i wondered if it might be a malware thingy as it seemed quite out of character, sorry Velocio.

    yeah its keywords being highlighted in loads of posts. One example is this: http://www.lfgss.com/post3038661-8.html the words slot and accomodations are both highlighted with links to various promotions to 'itext'

  • Yeah, there's no such content on the page or served from us.

    I wouldn't, I hate that stuff.

    Tell me though... if you access the same LFGSS content over https is it still there?

    If it is: Then it's a browser plugin doing it.
    If it isn't: Then it's a computer based malware or something on the network.

  • Tell me though... if you access the same LFGSS content over https is it still there?

    excuse my ignorance but whaddya mean?

    Im viewing it on Chrome if that helps...?

  • Try putting https:// before www.lfgss.com in the address bar.

    If it's secure, it's encrypted between your browser and my server. No-one can inject adverts into encrypted pages.

    Unless... the thing injecting adverts is inside your browser.

  • there arent any ads when i use https://

  • Then the malware isn't a browser plugin (it won't be fixed by removing all extensions and reinstalling the browser), it's something on your actual computer.

    At the very worst, it's on your network.

    But it's far more likely that it's on your computer.

    I'm going to assume Windows. You need to run anti-virus if you have it and/or any malware scanner such as Windows Defender.

  • cheers for that ill get on it

  • It could also be your ISP inserting the ads, some of them are buggers for that. If so, you'll get the same ads on a different computer using the same Internet connection.

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

Subtle changes, bugs and feedback

Posted by Avatar for Velocio @Velocio

Actions