Regexp::Common::URI::gopher man page on OpenServer

Man page or keyword search:  
man Server   5388 pages
apropos Keyword Search (all sections)
Output format
OpenServer logo
[printable version]

Regexp::Common::URI::gUserrContributed Perl DocuRegexp::Common::URI::gopher(3)

NAME
       Regexp::Common::URI::gopher -- Returns a pattern for gopher URIs.

SYNOPSIS
	   use Regexp::Common qw /URI/;

	   while (<>) {
	       /$RE{URI}{gopher}/	and  print "Contains a gopher URI.\n";
	   }

DESCRIPTION
       $RE{URI}{gopher}{-notab}

       Gopher URIs are poorly defined. Originally, RFC 1738 defined gopher
       URIs, but they were later redefined in an internet draft. One that was
       expired in June 1997.

       The internet draft for gopher URIs defines them as follows:

	   "gopher:" "//" host [ ":" port ] "/" gopher-type selector
			       [ "%09" search [ "%09" gopherplus_string ]]

       Unfortunally, a selector is defined in such a way that characters may
       be escaped using the URI escape mechanism. This includes tabs, which
       escaped are %09. Hence, the syntax cannot distinguish between a URI
       that has both a selector and a search part, and an URI where the selec-
       tor includes an escaped tab. (The text of the draft forbids tabs to be
       present in the selector though).

       $RE{URI}{gopher} follows the defined syntax. To disallow escaped tabs
       in the selector and search parts, use $RE{URI}{gopher}{-notab}.

       There are other differences between the text and the given syntax.
       According to the text, selector strings cannot have tabs, linefeeds or
       carriage returns in them. The text also allows the entire gopher-path,
       (the part after the slash following the hostport) to be empty; if this
       is empty the slash may be omitted as well. However, this isn't
       reflected in the syntax.

       Under "{-keep}", the following are returned:

       $1  The entire URI.

       $2  The scheme.

       $3  The host (name or address).

       $4  The port (if any).

       $5  The "gopher-path", the part after the / following the host and
	   port.

       $6  The gopher-type.

       $7  The selector. (When no "{-notab}" is used, this includes the search
	   and gopherplus_string, including the separating escaped tabs).

       $8  The search, if given. (Only when "{-notab}" is given).

       $9  The gopherplus_string, if given. (Only when "{-notab}" is given).

       head1 REFERENCES

       [RFC 1738]
	   Berners-Lee, Tim, Masinter, L., McCahill, M.: Uniform Resource
	   Locators (URL). December 1994.

       [RFC 1808]
	   Fielding, R.: Relative Uniform Resource Locators (URL). June 1995.

       [GOPHER URL]
	   Krishnan, Murali R., Casey, James: "A Gopher URL Format". Expired
	   Internet draft draft-murali-url-gopher. December 1996.

HISTORY
	$Log: gopher.pm,v $
	Revision 2.100	2003/02/21 14:40:59  abigail
	Gopher URLs

SEE ALSO
       Regexp::Common::URI for other supported URIs.

AUTHOR
       Damian Conway (damian@conway.org)

MAINTAINANCE
       This package is maintained by Abigail (regexp-common@abigail.nl).

BUGS AND IRRITATIONS
       Bound to be plenty.

COPYRIGHT
	    Copyright (c) 2001 - 2003, Damian Conway. All Rights Reserved.
	      This module is free software. It may be used, redistributed
	     and/or modified under the terms of the Perl Artistic License
		   (see http://www.perl.com/perl/misc/Artistic.html)

perl v5.8.8			  2003-03-23	Regexp::Common::URI::gopher(3)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server OpenServer

List of man pages available for OpenServer

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net