Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Jennifer Killingsworth 191 posts 248 karma points
    Feb 10, 2012 @ 14:57
    Jennifer Killingsworth
    0

    The URI prefix is not recognized

    Successfully checked a bunch of pages, but then we encountered this error: The URI prefix is not recognized.  At that point we can't get it to show any more pages with links to check -- just the error message.

  • Dan Diplo 1554 posts 6205 karma points MVP 6x c-trib
    Feb 12, 2012 @ 17:09
    Dan Diplo
    0

    Thanks for reporting this, Jennifer. Is that the full error message you get? Have you any idea what the links where that caused the problem? If it's a publicly accessible website then could you let me know the URL of the page in question, so I can try and work out what has caused this? Thanks.

  • Jennifer Killingsworth 191 posts 248 karma points
    Feb 14, 2012 @ 16:50
    Jennifer Killingsworth
    0

    That's the entire error message.

    The last page it successfully checked is: http://myfwc.com/fishing/freshwater/black-bass/fish-management-actions/

  • Jennifer Killingsworth 191 posts 248 karma points
    Feb 28, 2012 @ 15:20
    Jennifer Killingsworth
    0

    Any ideas?

  • Dan Diplo 1554 posts 6205 karma points MVP 6x c-trib
    Feb 28, 2012 @ 15:50
    Dan Diplo
    1

    Hi Jennifer,

    I had actually just got around to looking at this. I think I know what causes the error - it's basically when you have a link that contains a non-standard protocol. For instance, I found that <a href="about:blank">Blank</a> would cause it, since "about:" isn't a standard protocol.

    I hope to have a fix by end of day, which I will upload. I'll post here so you know.

    Dan

     

  • Dan Diplo 1554 posts 6205 karma points MVP 6x c-trib
    Feb 28, 2012 @ 16:48
    Dan Diplo
    1

    OK, I think I've fixed this. I've uploaded a new version of the package (1.1) which hopefully avoids this error.

    You should be able to install the package over the old one. Or you can extract the Diplo.LinkChecker.dll from the package file and overwrite the one in your /Bin folder.

    NB. The underlying problem was caused because the .NET Framework only supports "URIs that begin with http:, https:, ftp:, and file: scheme identifiers". See http://stackoverflow.com/questions/5182787/webrequest-results-with-uri-prefix-is-not-recognized for more info.

    Please let me know if it works for you!

    Dan

     

  • Jennifer Killingsworth 191 posts 248 karma points
    Feb 28, 2012 @ 17:23
    Jennifer Killingsworth
    0

    Yay!  I was able to get passed that last page and continue checking links.  Thanks for the fix! :)

  • Dan Diplo 1554 posts 6205 karma points MVP 6x c-trib
    Feb 28, 2012 @ 17:58
    Dan Diplo
    0

    Pleased it worked! :)

    I'll look at other features in the near future...

Please Sign in or register to post replies

Write your reply to:

Draft