Day: February 23, 2006

  • MarcEdit 5.0 update

    To deal with servers that provide either http headers in invalid formats or servers that use proxies with expired certificates, I ended up having make a few adjustments to the Verify URL utility.  To get an indepth explaination of what changes were made, please see: Dealing with expired security certificates: https://blog.reeset.net/archives/166 Dealing with invalid http…

  • Dealing with malformed http headers

    If you have a link checker, you invariably want to just read page headers.  Well, in .NET, they enforce a very strict interpretation of the HTTP header standard.  Unfortunately, a great number of servers (Innovative Interface’s ILS for one), don’t follow the output rules, so .NET’s HTTPWebRequest object will throw a webexception when requesting headers…

  • Dealing with expired certificates and .NET’s HTTPWebRequest object

    Some folks that had tried using the Verify URL utility had notified me that it wasn’t reporting a response status when attempting to query materials through an ezproxy url.  The problem it appears, was that the servers in question had either expired security certificates or certificates that were not issued by a trusted site (i.e.,…