Couple things I noticed:
When I visit (for example) the DIRECTIONS page via HTTPS, then click the CALENDAR link, I'm 302 redirected to HTTP. Not sure if that's intentional. (Best way to see it is with Safari or Chrome's 'Network' tab in the developer tools window).
Also, Chrome seems to think something is being loaded insecurely on this page: https://www.dnalounge.com/calendar/2012/07-05.html
Maybe the thumbnail on the youtube clip?
Also, a question on housekeeping: Would you rather that dnalounge comments stayed on dnalounge.com or is here fine?
Thanks, I've fixed the video thing.
I don't see any way to fix the "Calendar" thing because the way that works is there is a line in .htaccess that says:
Redirect 302 /calendar/latest.html http://www.dnalounge.com/calendar/2012/08.html
and leaving off the protocol, making it //www.dnalounge.com/..., doesn't work. Redirect directives need to be fully-qualified URLs.
Doesn't matter to me where you comment.
Redirect directives need to be fully-qualified URLs.
The manual says: " The new URL should be an absolute URL beginning with a scheme and hostname, but a URL-path beginning with a slash may also be used, in which case the scheme and hostname of the current server will be added." - Apache 2.2, Redirect.
Which sounds like "Redirect 302 /calendar/latest.html /calendar/2012/08.html" should work; this is in line with the example under "Discussion" here Apache 2.2, Rewriting From Old to New: "Redirect /foo.html /bar.html"
Cool! That works, thanks.