: @
go:
は
coap: coaps: ftp: http: https: wais: ws: wss: z39.50r: z39.50s: prospero:ci: dvb: reload: docker: は
tweetbot: wpp: ni: :// を続けたためだけに形式的に存在するのみで、
実質的には
amb: bookpedia: byword: callrec: cartographer: cdpedia: cheapcalls: cloudrop: cobitools: dailymotion: define: duoxx: dvdpedia: editorial eureka: fb: gamepedia: gcbuddy: geopherlite: imagedata: izorn: kippster: launchpro-dropbox: localch: mail: mypraypal: navigon: pic2shop: purecalc: radarscope: roundtuit: x-seesmic: simplenote: surfboard: threadnote: tikisurf: timelog: twitter: ugomemo: unfragment: yummy: zentap: zentappro: dat:async:cache:crypto:concat:tee:
[ ]
While the syntax for the rest of the URL may vary depending on the particular scheme selected, URL schemes that involve the direct use of an IP-based protocol to a specified host on the Internet use a common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
Some or all of the parts "<user>:<password>@", ":<password>", ":<port>", and "/<url-path>" may be excluded. The scheme specific data start with a double slash "//" to indicate that it complies with the common Internet scheme syntax. The different components obey the following rules:
- user
- An optional user name. Some schemes (e.g., ftp) allow the specification of a user name.
- password
- An optional password. If present, it follows the user name separated from it by a colon.
The user name (and password), if present, are followed by a commercial at-sign "@". Within the user and password field, any ":", "@", or "/" must be encoded.
Note that an empty user name or password is different than no user name or password; there is no way to specify a password without specifying a user name. E.g.,
URL:ftp://@host.com/ has an empty user name and no password,URL:ftp://host.com/ has no user name, whileURL:ftp://foo:@host.com/ has a user name of "foo" and an empty password.
- host The fully qualified domain name of a network host, or its IP address as a set of four decimal digit groups separated by ".". Fully qualified domain names take the form as described in Section 3.5 of RFC 1034 [13] and Section 2.1 of RFC 1123 [5]
- a sequence of domain labels separated by ".", each domain label starting and ending with an alphanumerical character and possibly also containing "-" characters. The rightmost domain label will never start with a digit, though, which syntactically distinguishes all domain names from the IP addresses.
- port
- The port number to connect to. Most schemes designate protocols that have a default port number. Another port number may optionally be supplied, in decimal, separated from the host by a colon. If the port is omitted, the colon is as well.
- url-path
- The rest of the locator consists of data specific to the scheme, and is known as the "url-path". It supplies the details of how the specified resource can be accessed. Note that the "/" between the host (or port) and the url-path is NOT part of the url-path.
The url-path syntax depends on the scheme being used, as does the manner in which it is interpreted.
If the parse string begins with a double-slash "//", then the substring of characters after the double-slash and up to, but not including, the next slash "/" character is the network location/login (<net_loc>) of the URL. If no trailing slash "/" is present, the entire remaining parse string is assigned to <net_loc>. The double-slash and <net_loc> are removed from the parse string before continuing.
解析文字列が二重斜線 // から始まる場合、その二重斜線から次の斜線 / 文字の手前までの部分文字列が URL のネットワーク位置・ログイン (/ がない場合には、解析文字列の残りの部分全体が net_loc に割り当てられます。
二重斜線及び net_loc は、続行する前に解析文字列から削除します。
Many URI schemes include a top hierarchical element for a naming authority, such that the namespace defined by the remainder of the URI is governed by that authority. This authority component is typically defined by an Internet-based server or a scheme-specific registry of naming authorities.
多くの URI scheme は、最上位階層要素として命名権者を含めており、 URI の残りの部分で定義される名前空間はその命名権者の領めるところとなります。 この命名権者部品は、典型的にはインターネットを基にしたサーバー又は scheme 定義の命名権者登録簿により定義されます。
authority = server | reg_name
The authority component is preceded by a double slash "//" and is terminated by the next slash "/", question-mark "?", or by the end of the URI. Within the authority component, the characters ";", ":", "@", "?", and "/" are reserved.
命名権者部品は前に二重斜線 // がつき、
次の斜線 /, 疑問符 ?
又は URI の末端により終端されます。
命名権者部品中では、文字 ;,
:, @,
?, / が
An authority component is not required for a URI scheme to make use of relative references. A base URI without an authority component implies that any relative reference will also be without an authority component.
命名権者部品は、 URI scheme が相対参照を使うために必須ではありません。
命名権者部品なしの
The structure of a registry-based naming authority is specific to the URI scheme, but constrained to the allowed characters for an authority component.
登録簿を基にした命名権者は URI scheme に特有のものですが、 命名権者部品で許される文字に制約されます。
reg_name = 1*(unreserved |escaped | "$" | "," | ";" | ":" | "@" | "&" | "=" | "+" )
URL schemes that involve the direct use of an IP-based protocol to a specified server on the Internet use a common syntax for the server component of the URI's scheme-specific data:
インターネットの特定のサーバーに対する IP を基にしたプロトコルの直接使用を含んだ URL scheme は、 URI の scheme 特定データのサーバー部品に共通の構文を使います。
<userinfo>@<host>:<port>
where <userinfo> may consist of a user name and, optionally, scheme-specific information about how to gain authorization to access the server. The parts "<userinfo>@" and ":<port>" may be omitted.
ここで、 userinfo は利用者の名前を入れることができて、任意選択によって、サーバーに接続するための認証の方法についての scheme 特有の情報をも入れることができます。
<userinfo>@ の部分と :<port> の部分アh省略可能です。
server = [ [] ]]userinfo "@"[hostport
The user information, if present, is followed by a commercial at-sign "@".
利用者情報を示す場合は、その後に単価記号 @ が続きます。
userinfo = *(unreserved |escaped | ";" | ":" | "&" | "=" | "+" | "$" | "," )
Some URL schemes use the format "user:password" in the userinfo field. This practice is NOT RECOMMENDED, because the passing of authentication information in clear text (such as URI) has proven to be a security risk in almost every case where it has been used.
URL scheme によっては、 userinfo
欄に user:password の書式を使います。
この慣習は、認証情報を
The host is a domain name of a network host, or its IPv4 address as a set of four decimal digit groups separated by ".". Literal IPv6 addresses are not supported.
. で分離した4つの10進数集団の集合としたものです。
生
hostport = host [ ":"port ]host = hostname |IPv4address hostname = *( domainlabel "." ) toplabel [ "." ]domainlabel =alphanum | alphanum *( alphanum | "-" ) alphanumtoplabel = alpha | alpha *( alphanum | "-" ) alphanumIPv4address = 1*digit "." 1*digit "." 1*digit "." 1*digitport = *digit
Hostnames take the form described in Section 3 of [RFC1034] and Section 2.1 of [RFC1123]: a sequence of domain labels separated by ".", each domain label starting and ending with an alphanumeric character and possibly also containing "-" characters. The rightmost domain label of a fully qualified domain name will never start with a digit, thus syntactically distinguishing domain names from IPv4 addresses, and may be followed by a single "." if it is necessary to distinguish between the complete domain name and any local domain. To actually be "Uniform" as a resource locator, a URL hostname should be a fully qualified domain name. In practice, however, the host component may be a local domain literal.
ホスト名は、 RFC 1034 の3章と RFC 1123 の2.1章で説明されている形を取りました。 . で分離されたドメイン札の連続体で、それぞれのドメイン札は英数字で始まり英数字で終わり、 - を含めることもできます。. を続けることができます。
真に「統一」された資源位置子であるためには、 URL
ホスト名は完全修飾名であるべきです。しかし、実際にはホスト部品は局所ドメイン札かもしれません。
Note: A suitable representation for including a literal IPv6 address as the host part of a URL is desired, but has not yet been determined or implemented in practice.
注意 : URL のホスト部分として生 IPv6 アドレスを含める適当な表現が望まれますが、まだ決定していませんし実際に実装されてもいません。
The port is the network port number for the server. Most schemes designate protocols that have a default port number. Another port number may optionally be supplied, in decimal, separated from the host by a colon. If the port is omitted, the default port number is assumed.
port は、サーバーのネットワーク・ポート番号です。ほとんどの scheme は既定ポート番号のあるプロトコルを指示しています。
他のポート番号は省略可能ですが10進数で host
とコロンで区切って指定して構いません。
port が省略されている時には、
既定ポート番号が仮定されます。
→
http https [#XERCESJ-1060] anyURI validation is too strict - ASF JIRA
Reg-name conflict between 2396 and 3986
(
2007-01-23 20:48:55 +09:00 版)
2007-01-23 20:46:26 +09:00 版)
2007-02-22 09:21:45 +09:00 版)
2007-02-22 09:23:49 +09:00 版)
2007-02-22 09:21:53 +09:00 版)
The following connects to a replica set with three members running on localhost on ports 27017, 27018, and 27019:
mongodb://localhost,localhost:27018,localhost:27019
or as a UNIX-domain socket path specified after the word “unix” and enclosed in colons:
proxy_pass http://unix:/tmp/backend.socket:/uri/;
1. We need to define a mechanism for using IPv6 addresses in the
URL hostname which will not break existing systems too badly.
Proposal: *hex *["." *hex] ".ipv6"
I.e., treat the top level domain of "ipv6" as special.
Note: host name matching in the Android framework is case-sensitive, unlike the formal RFC. As a result, you should always specify host names using lowercase letters.
RL
schemes which do not contain a conformant hierarchical structure in
their <scheme-specific-part> should not use double slashes following
the "<scheme>:" string.
Avoid improper use of "//". The use of double slashes in the first
part of a URI is not an artistic indicator that what follows is a
URI: Double slashes are used ONLY when the syntax of the URI's
<scheme-specific-part> contains a hierarchical structure as described
in RFC 3986. In URIs from such schemes, the use of double slashes
indicates that what follows is the top hierarchical element for a
naming authority. (See Section 3.2 of RFC 3986 for more details.)
URI schemes that do not contain a conformant hierarchical structure
in their <scheme-specific-part> SHOULD NOT use double slashes
following the "<scheme>:" string.
Schemes SHOULD avoid improper use of "//". The use of double slashes
in the first part of a URI is not a stylistic indicator that what
follows is a URI: double slashes are intended for use ONLY when the
syntax of the <scheme-specific-part> contains a hierarchical
structure. In URIs from such schemes, the use of double slashes
indicates that what follows is the top hierarchical element for a
naming authority (Section 3.2 of RFC 3986 has more details). Schemes
that do not contain a conformant hierarchical structure in their
<scheme-specific-part> SHOULD NOT use double slashes following the
"<scheme>:" string.
With PostgreSQL, you can also use unix domain socket paths with percent encoding: postgres://%2Fvar%2Flib%2Fpostgresql/dbname.
xri://@!a!b*(mailto:jd@example.com)*e/f
◎許諾されたURLと一致しないWebサイトで使用された場合、契約外使用として違約金が科せられます。使用するURLの第一階層をすべてお知らせください。また、同一のスポンサー名・商品名を冠した同一レイアウトのWebサイトであっても、URLが違う場合は他者の使用と判断されます。特に、ショッピングモール等通販サイトやグローバルサイトのURLについてはご注意ください。
【 一階層 = http://に続く次のスラッシュまでのURL/】