… = <value, defined in [RFC2616] Section 3.6 ; token | quoted-string Defined in [RFC5987] ext-value = <ext-value, defined in [RFC5987] Section 3.2 Content-Disposition header field values with multiple instances of the same parameter name are invalid. Note that due to the rules for…

… <value, defined in [RFC2616], Section 3.6> ; token | quoted-string Defined in [RFC5987]: ext-value = <ext-value, defined in [RFC5987], Section 3.2> Content-Disposition header field values with multiple instances of the same parameter name are invalid. Note that due to the rules …

… <value, defined in [RFC2616], Section 3.6 ; token | quoted-string Defined in [ RFC5987 ]: ext-value = <ext-value, defined in [RFC5987], Section 3.2 Content-Disposition header field values with multiple instances of the same parameter name are invalid. Note that due to the rules …

…field, MAY be extended to ISO 10646-1 values using the framework described in [ RFC5987 ]. All servers and clients MUST be capable of receiving and sending values encoded per the syntax specified in [ RFC5987 ]. If a value to be sent contains only ASCII characters, the field MUST…

…C.REC-html401-19991224 ]: MediaDesc; from [ RFC5646 ]: Language-Tag; and from [ RFC5987 ], ext-value and parmname. Nottingham Standards Track [Page 3] RFC 5988 Web Linking October 2010 3 . Links In this specification, a link is a typed connection between two resources that are id…

… [W3C.REC-html401-19991224]: MediaDesc; from [RFC5646]: Language-Tag; and from [RFC5987], ext-value and parmname. Nottingham Standards Track [Page 3] RFC 5988 Web Linking October 2010 3. Links In this specification, a link is a typed connection between two resources that are iden…

…C.REC-html401-19991224 ]: MediaDesc; from [ RFC5646 ]: Language-Tag; and from [ RFC5987 ], ext-value and parmname. Nottingham Standards Track [Page 3] RFC 5988 Web Linking October 2010 . Links In this specification, a link is a typed connection between two resources that are iden…

… name can be sent with this parameter, using the extended notation defined in [ RFC5987 ]. realm See "realm" definition in Section 3.3 uri The Effective Request URI ( Section 5.5 of [RFC7230] ) of the HTTP request; duplicated here because proxies are allowed to change the request…

…C.REC-html401-19991224 ]: MediaDesc; from [ RFC5646 ]: Language-Tag; and from [ RFC5987 ], ext-value and parmname. Nottingham Standards Track [Page 3] RFC 5988 Web Linking October 2010 . Links In this specification, a link is a typed connection between two resources that are iden…

… name can be sent with this parameter, using the extended notation defined in [ RFC5987 ]. realm See "realm" definition in Section 3.3 uri The Effective Request URI ( Section 5.5 of [RFC7230] ) of the HTTP request; duplicated here because proxies are allowed to change the request…

…e:" URI URI-SCHEME ] might be encoded. NOTE: The encoding method described in [ RFC5987 ], which would add a "filename*" parameter to the Content-Disposition header field, MUST NOT be used. Some commonly deployed systems use multipart/form-data with file names directly encoded in…

…oses to represent parameters. Both MIME [RFC2045] [RFC2231] and HTTP [RFC2045] [RFC5987] allow binary parameters as well as parameter values expressed in a specific charset, but other protocols may be less flexible. New parameters SHOULD NOT be defined as a way to introduce new f…

… a greater range of characters can use an encoding such as the one defined in [ RFC5987 ]. Because commas (",") are used as a generic delimiter between field- values, they need to be treated with care if they are allowed in the field-value's payload. Typically, components that mi…

…g a greater range of characters can use an encoding such as the one defined in [RFC5987] Leading and trailing whitespace in raw field values is removed upon field parsing ( Section 3.2.4 of [RFC7230] ). Field definitions where leading or trailing whitespace in values is significa…

… a greater range of characters can use an encoding such as the one defined in [ RFC5987 ]. Leading and trailing whitespace in raw field values is removed upon field parsing ( Section 3.2.4 of [RFC7230] ). Field definitions where leading or trailing whitespace in values is signifi…