Handling of url's that contain a port number

[glen]

Hi

How do you handle a url which has a port number in it -

http://xbz.com:8080/index.php

Which all lookup's are necessary?
There is no information in the Docs.

Thanks
Glen

[Richard Anthony Webley]

Strange one that.

 

When the average user surfs the internet under most circumstances they would never need to enter a url with a port. That function is normally reserved for accessing a remote site for purposes of remote administration.

 

i.e, using the example you have given   -   url:8080 the port 8080 is normally reserved for remotely administering a router.

 

So to recap for day-to-day surfing the average user would never have a need to include a port number. Anyone using a port number would be assumed to be connecting to a valid / known remote site anyway.

 

Regards,

 

 Richard

Regards,

 

 Richard Anthony Webley.

[glen]

Yes a user would never need to do that.
But I am monitoring if a malicious script tag is injected into a page
with a link to a url. I need to check if the url is part of the Google
SafeBrowing Databse.

Thanks
Glen

On Oct 7, 2:58 pm, "Richard Anthony Webley"

[Stratsimir Kolchevski]

Did you read carefully? :-)
http://code.google.com/apis/safebrowsing/developers_guide.html:
"The scheme, username, password, and port are disregarded."

[glen]

Whoops missed that line.

Thanks
Glen

On Oct 7, 5:06 pm, Stratsimir Kolchevski <stratsi...@gmail.com> wrote:
> On Oct 7, 12:36 pm, glen <glen.noro...@gmail.com> wrote:
>
> > Hi
>
> > How do you handle a url which has a port number in it -
>
> >http://xbz.com:8080/index.php
>
> > Which all lookup's are necessary?
> > There is no information in the Docs.
>

> Did you read carefully? :-)http://code.google.com/apis/safebrowsing/developers_guide.html: