Blackrock Networks, Inc.

Category: IE Compatibility

  • Blackrock Networks, Inc. and Constant Contact end old browser support

    LOTS TO KNOW THIS WEEK

    END OF LIFE for Windows XP: On April 8, 2014, support and updates from Microsoft for Windows XP will no longer be available. Don’t let your PC go unprotected.

    Time to upgrade your browser.
    On March 31st Constant Contact and Blackrock Networks, Inc. will stop supporting some older browser versions.

    Get the latest versions below.

    What Does “Support” Mean

    Support means that we will no longer fix issues that are specific to the older browsers. You older browser will still work, but you may experience issues.

    Like at  www.facebook.com/blackrocknetworks for system updates.

    Or +1 us on Google at www.google.com/+Blackrocknetworks for our great video tutorials and updates.

  • Windows 8 and Internet Explorer 10

    There have been  reports that  drop-down menus on some website aren’t working with Windows 8. The issue in not Windows 8 per say, but with the version of  Internet Explorer 10 that it ships with.  To fix this, open up Internet Explorer from the desktop. Go to the menu bar, click > Tools > Compatibility > View Settings. Add the website you have having problems with to that list and then click close. This should bring the drop-down menu back. Now it is time to contact us to bring your website up to speed with the latest browsers so your users don’t have to do this.

  • Internet Explorer Compatibility View – Turn On or Off

    Websites that were designed for earlier versions of Internet Explorer might not display correctly in the IE8 (and above) version included in Windows 7. When you turn on Compatibility View, the webpage you’re viewing, as well as any other webpages within the website’s domain, will be displayed as if you were using an earlier version of Internet Explorer.

    See image below. NOTE: The webpage will refresh with Compatibility View turned either on or off.

  • SSL

    Although having an SSL certificate can present certain user errors in regards to notification from older browsers certificate-authenticated SSL is considered mandatory by all security guidelines whenever a web site hosts confidential information or performs material transactions.

    WildCard Domains:

    Unfortunately there has never been a good RFC on how wildcard matching works so the different implementations (SChannel and NSS mainly) are slightly different. However, here’s the draft standard which will pin this down:

    http://tools.ietf.org/html/draft-saintandre-tls-server-id-check-09#section-4.4.3

    And here’s Microsoft’s take on it:

    http://support.microsoft.com/kb/258858

    Accepted wildcard examples

    • www.example.com matches www.example.com
    • *.example.com matches www.example.com
    • w*.example.com matches www.example.com
    • ww*.example.com matches www.example.com
    • Www.Example.com matches www.examPle.cOm

    Nonaccepted wildcard examples

    • *www.example.com
    • *w.example.com
    • w*w.example.com
    • *ww.example.com does not match www.example.com
    • www.e*ample.com does not match www.example.com
    • www.*ample.com does not match www.example.com
    • www.ex*.com does not match www.example.com
    • www.*.com does not match www.example.com
    • example.com does not match *.com does not match www.example.com
    • www.example.abc.com does not match *.abc.com
    • example.com does not match *.*
    • example does not match *
    • abc.def.example.com does not match a*.d*.example.com
    • www.example.com.au does not match *.*.com.au
    • www.example.com.au does not match www.*.com.au

    Basically, a wildcard may appear as the left-most label and it matches exactly one label. So *.example.com matches www.example.com, but not example.com (because that would mean matching zero labels).