Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 3324 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Policy test URL validation missing tld

Roderick Pechey

Hi All

Does anyone know how to resolve this issue please?

Using the Policy Test to check a user's access to a url is giving an error message of "Please enter a valid protocol://address:port url"
The url is https://aaa.aaaaaa.hosting/aaaaaaaa.
If I change just the tld in the url, to say, https://aaa.aaaaaa.com/aaaaaaaa, or any other common tld it's happy.

I'm guessing the url's being parsed & compared to a list of tlds as I type?
Is it a list we can edit?
If not, any idea who maintains it?


Many thanks.



This thread was automatically locked due to age.
Parents
  • 0

    Hello Roderick,

    Our WingC will try to determine the category, could you test the URL and check the category shown in the log viewer. The Policy test may show some discrepancy in the actual performance.

  • 0 in reply to Aditya Patel

    Hi Aditya

    The category comes up as 'None'.
    Would the actual URL be of any significant use?


    Many thanks for looking into it.

  • 0 in reply to Roderick Pechey

    Hello Roderick,

    If the category is not known then we would need to categorize it on request. Other than that there would not be significant unless the URL is public and clients have set to block none category.

  • 0 in reply to Aditya Patel

    Hi Aditya

    I'm not understanding what the category has got to do with it unfortunately.
    The fact its category is 'None' just means that it gets blocked by default on our system & we add it to an allowed url group.

    The issue is that as soon as I put in ANY url that has a tld of 'hosting' the Policy Test tool tells me that I have entered an invalid URL.
    It could have a category of anything, but if the Policy Test tool will not accept it as a valid url then I can't test the results of anything I do to affect access to it.

    This is a Policy Test tool issue not a categorisation issue surely?

    Not a valid URL according to the tool


     

    A valid URL according to the tool



    Many thanks.

  • 0 in reply to Roderick Pechey

    Hello Roderick,

    It does seem we have a limitation on the number of characters the tld would support and found it to be 6 characters. 

    so in otherwords, the policy test has some restrictions and would work if tld<7 characters. In this case "hosting" is 8 characters and would work with 6 or less characters.

Reply
  • 0 in reply to Roderick Pechey

    Hello Roderick,

    It does seem we have a limitation on the number of characters the tld would support and found it to be 6 characters. 

    so in otherwords, the policy test has some restrictions and would work if tld<7 characters. In this case "hosting" is 8 characters and would work with 6 or less characters.

Children