Update, October 2017 Anyone using our comment notification system, Microsoft (Hotmail) is blocking the IP we use to email your notifications. Am attempting to fix, but it’s Microsoft, so who knows how long it’ll be for the fix, if ever. I’ll keep watching, if necessary we’ll do something else to fix. Apologies from me if you’ve been wondering why you’re not getting any notifications.
Further, if you don’t like getting your comment notifications, please don’t mark the emails as “Junk” in Outlook or Gmail as doing so may trigger their systems to block our IP. Instead, just contact me and I’ll remove you from the notifications system. For contact, use menu option above.
Update, November 20. Things seem to be better though we’re still getting reports from folks who’s browsers are doing too good a job of caching the site. We’re still working on our end, that’s why I didn’t quite get this morning’s blog post done (perhaps this afternoon). If you are still experiencing problems (old posts showing, new ones not appearing when you browse to site), at the least do a cold boot of your computer and use the refresh option for your browser. Apparently some folk’s browsers cached our former cache settings, or something like that. So the refresh can “stick.” Fortunately, as indicated by our server metrics most of you are having no problems, but I want it to work for everyone, so thanks for any ongoing feedback.
Original post: Calling all WildSnow readers. I’ve been playing around with website server settings to deal with “traffic storms” such as when we published the Jetforce Airbag post. Apparently something I did might make the site tend to stay cached on your browser without refreshing easily enough. In other words, you might exit the site, then return, and everything looks the same even though there is actually a new blog post and/or new comments.
One user said they were having to refresh their browser cache (by clicking the refresh icon, or hitting F5) to be able to see any changes, even though they had exited and returned to the site. Meaning the site caching is working a little too well.
Anyone experiencing any inconvenient site behavior due to how it browser caches?
Thanks all, Lou