RFC 4387 - Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTP ( 版) http://tools.ietf.org/html/rfc4387#section-2
[14]
Specifying time intervals in URI queries and fragments of time-based Web resources (2006-05-06 10:39:46 +09:00 版) http://annodex.net/TR/URI_fragments.html#rfc.section.3
[194] hypertext references and the query component
(Erik van der Poel 著, 版)
http://lists.w3.org/Archives/Public/public-iri/2009Jul/0008.html
[209] Media Fragments URI 1.0 (basic) ( 版) http://www.w3.org/TR/2012/REC-media-frags-20120925/#standardisation-terminology
URI query: The query component is indicated by the first question mark ("?") character and terminated by a number sign ("#") character or by the end of the URI.
[19] RFC 7472 - Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme ( 版) https://tools.ietf.org/html/rfc7472#section-4.2
The information which follows the ? in the URL which referenced this script. This is the query information. It should not be decoded in any fashion. This variable should always be set when there is query information, regardless of command line decoding.
A URL-encoded string; the <query> part of the Script-URI. (See section 3.2.)
URL 符号化文字列: Script-URI
の <query>
部分です。
QUERY_STRING = query-string
query-string = *uric
The URL syntax for a query string is described in section 3 of RFC 2396 [4].
問合せ文字列の URL 構文は
RFC2396の3章で説明されています。
Servers MUST supply this value to scripts. The QUERY_STRING value is case-sensitive. If the Script-URI does not include a query component, the QUERY_STRING metavariable MUST be defined as an empty string ("").
[211] Bug 23822 – Should the EventSource, Worker, and SharedWorker constructors resolve the URL using utf-8?
( ( 版))
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23822
[212] Clean up set the input algorithm now all URLs have a query · 217cf06 · whatwg/url
( ( 版))
https://github.com/whatwg/url/commit/217cf06b9d2b7fbbbf65eec9d1ea9fce66fec8bf
[20] Do not encode ` in query. Fixes #17. · whatwg/url@f54c44d
( 版)
https://github.com/whatwg/url/commit/f54c44d1f790dd2b8913e955ba6d334c6f14a048
[52] Comment out query/queryAll/Elements for now · whatwg/dom@10b6cf1
( 版)
https://github.com/whatwg/dom/commit/10b6cf1ba02806220d5461a3bdb7939728b73635
[66] Align with changes in Selectors
( (annevk著, ))
https://github.com/whatwg/dom/commit/1594aa52357371354780750413ad88e9e8a2b56b
[67] 284474 – Converting to UTF-8 a url with an unescaped non-ASCII chars in the query part leads to an incompatibility with most server-side programs
( ())
https://bugzilla.mozilla.org/show_bug.cgi?id=284474
[70] Apache Tomcat Configuration Reference (6.0.45) - The HTTP Connector
(Craig R. McClanahan著, )
http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
URIEncoding
This specifies the character encoding used to decode the URI bytes, after %xx decoding the URL. If not specified, ISO-8859-1 will be used.
useBodyEncodingForURI
This specifies if the encoding specified in contentType should be used for URI query parameters, instead of using the URIEncoding. This setting is present for compatibility with Tomcat 4.1.x, where the encoding specified in the contentType, or explicitly set using Request.setCharacterEncoding method was also used for the parameters from the URL. The default value is false.
[71] Editorial: give URL syntax components their own terms
(annevk著, )
https://github.com/whatwg/url/commit/451696e4297c4c676fae21dbc926aeafb2477e6c
[73] Signature Calculations for the Authorization Header: Transferring Payload in a Single Chunk (AWS Signature Version 4) - Amazon Simple Storage Service
()
http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html
CanonicalQueryString specifies the URI-encoded query string parameters. You URI-encode name and values individually. You must also sort the parameters in the canonical query string alphabetically by key name. The sorting occurs after encoding.
[74] Web Annotation Protocol
()
https://w3c.github.io/web-annotation/protocol/wd/#h-container-representations
The IRI of the Container provided in the response should differentiate between whether the pages contain just the IRIs, or the full descriptions of the Annotations. It is recommended that this be done with a query parameter.
All API.AI requests should be made with the versioning v parameter in the URL.
The approach is similar to the Foursquare versioning policy. So, for example, the query requests should be made to the endpoint /query?v=20150910.
The v parameter is formatted as YYYYMMDD.
The parameter indicates that you are ready to handle API version as of the specified date.
[76] documentation/API.md at master · tootsuite/documentation
()
https://github.com/tootsuite/documentation/blob/master/Using-the-API/API.md
When an array parameter is mentioned, the Rails convention of specifying array parameters in query strings is meant. For example, a ruby array like foo = [1, 2, 3] can be encoded in the params as foo[]=1&foo[]=2&foo[]=3. Square brackets can be indexed but can also be empty.
[77] java - Tomcat 8 is not able to handle get request with '|' in query parameters? - Stack Overflow
( ())
http://stackoverflow.com/questions/41053653/tomcat-8-is-not-able-to-handle-get-request-with-in-query-parameters
In most cases this should work. Treating semi-colons and '&' in queries identically is recommended by the World Wide Web Consortium (W3C). Note that due to the nature of the URL, you may have to specify the name of the downloaded file as well:
Subscribers MAY also include additional HTTP [RFC7230] request parameters, as well as HTTP [RFC7230] Headers if they are required by the hub.
Hubs MUST ignore additional request parameters they do not understand.
[88] 62273 – Add support for alternate URL specification
()
https://bz.apache.org/bugzilla/show_bug.cgi?id=62273
[89] Change query state slightly to better deal with non-UTF-8 encodings
(annevk著, )
https://github.com/whatwg/url/commit/f0e4390bf882446445e944215524ff3877aac95a
[91] Change query state slightly to better deal with non-UTF-8 encodings by annevk · Pull Request #386 · whatwg/url
()
https://github.com/whatwg/url/pull/386
[92] 795733 - '&' and ';' should not be percent-encoded in URL queries - chromium - Monorail
()
https://bugs.chromium.org/p/chromium/issues/detail?id=795733
[93] Editorial: avoid setting encoding multiple times
(annevk著, )
https://github.com/whatwg/url/commit/b385374e5d1b48f82b8040395786469ae655f435
[94] Change query state slightly to better deal with non-UTF-8 encodings by annevk · Pull Request #386 · whatwg/url
()
https://github.com/whatwg/url/pull/386
[95] Percent-encode ' in queries of URLs with special schemes
(achristensen07著, )
https://github.com/whatwg/url/commit/6ef17ebe1220a7e7c0cfff0785017502ee18808b
[96] percent-encode ' in queries of URLs with special schemes · Issue #348 · whatwg/url
()
https://github.com/whatwg/url/issues/348
[97] percent-encode ' in queries of URLs with special schemes by achristensen07 · Pull Request #395 · whatwg/url
()
https://github.com/whatwg/url/pull/395
[98] Change query state slightly to better deal with non-UTF-8 encodings
(annevk著, )
https://github.com/whatwg/url/commit/f0e4390bf882446445e944215524ff3877aac95a