Help-Site Computer Manuals
Software
Hardware
Programming
Networking
  Algorithms & Data Structures   Programming Languages   Revision Control
  Protocols
  Cameras   Computers   Displays   Keyboards & Mice   Motherboards   Networking   Printers & Scanners   Storage
  Windows   Linux & Unix   Mac

/var/sites/help-site.com/auto/tmp/CPAN/9677/Link_Controller-0.037/lib/WWW/Link_Controller/URL.pm

/var/sites/help-site.com/auto/tmp/CPAN/9677/Link_Controller-0.037/lib/WWW/Link_Controller/URL.pm


link_url

link_url looks at a candidate.

verify_url

verify url checks that a url is a valid and possible uri in the terms of RFC2396

untaint_url

Used in our CGI bin programs, untaint_url takes a scalar and returns it untainted if and only if it's contains only valid url characters and it is a valid url according to verify_url.

A fundamental assumption in using this function is that your software can handle anything which looks like a valid URL, even if it isn't a valid url. E.g. news://www.a.b.com/directory/otherdir.

verify_fragment

Fragments have fairly free syntax but RFC 2396 says clearly they should conform to the same character set as URIs. Unfortunately, it seems that many people put spaces in their fragments in contradiction with the RFC since it works in HTML in practice.

We choose not to accept those and people should be able to change over?

If it turns out, as it probably will, that there is a real need for spaces in cross references to other people's documents which can't be fixed then maybe we will have to reconsider.

Programminig
Wy
Wy
yW
Wy
Programming
Wy
Wy
Wy
Wy