RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
0 sources
RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
Summary
RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) is a Request for Comments[1].
Key Facts
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) authored Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) — author (P50): Julian Reschke[2].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s instance of is recorded as Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) — instance of (P31): Request for Comments[3].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s publisher is recorded as Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) — publisher (P123): Internet Engineering Task Force[4].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s based on is recorded as Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) — based on (P144): RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1[5].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s DOI is recorded as 10.17487/RFC6266[6].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s language of work or name is recorded as Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) — language of work or name (P407): English[7].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s publication date is recorded as +2011-06-01T00:00:00Z[8].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s RfC ID is recorded as 6266[9].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc6266[10].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc6266.txt[11].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6266.txt[12].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6266.txt.pdf[13].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s number of pages is recorded as {'unit': '1', 'amount': '+14'}[14].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s title is recorded as Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)[15].
- RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s DBLP publication ID is recorded as journals/rfc/rfc6266[16].
Body
Designation and Status
RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)'s instance of is recorded as Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) — instance of (P31): Request for Comments[3].