文章分类 | 推荐文章 | 最新文章 | 热点文章 | 最新软件 | 精品软件 | 下载排行 | 推荐下载 | firefox | WPS | 杀毒软件 | Picasa
清风网络
首 页 软件下载 网络学院 数码学院
QQ 电脑入门 游戏 操作系统 图形处理 办公软件 媒体动画 精文荟萃 工具软件 网络编程 程序开发 网络技术 认证考试 网站建设 文章专栏
当前位置:清风网络学院网络技术网络协议RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1
精品推荐
特别推荐
·ISIS路由协议
·Telnet入侵最完全手册
·网络协议基础知识 SMTP协议和UDP协议
·新的宽带认证方式——IEEE 802.1x协议
·ARP协议揭密
·网络沟通的桥梁-协议X档案
·TCP/IP协议简介
·NGN网络协议解析
·HTTP协议基础
·电子商务安全协议
·SSL协议介绍
·SIP、SAP及SDP协议组合应用的研究
·在Windows 2000 Server中配置TCP/IP协议
·Catalyst8500配置实例之HSRP协议培植
·计算机网络体系层次结构的划分
·OSPF计算路由
热点TOP10
·RFC1305 - Network Time Protocol (Version 3) Specification, Implementation
·RFC1015 - Implementation plan for interagency research Internet
·Ad Hoc网络协议栈通用要求研究
·RFC791 - Internet Protocol
·RFC4081 - Security Threats for Next Steps in Signaling (NSIS)
·完全用Linux工作 摈弃Windows
·在Windows 2000 Server中配置TCP/IP协议
·关于Sniffer Pro
·RFC4098 - Terminology for Benchmarking BGP Device Convergence in the Control Plane
·RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1
·第三章 广域网协议配置命令(四)
·RFC3996-Internet Printing Protocol (IPP): The ippget Delivery Method for Event Notifications
·RFC2753 - A Framework for Policy-based Admission Control
·Telnet入侵最完全手册
·ARP(地址解析协议)的高速缓存、分组格式和代理以及arp命令
·RFC2765 - Stateless IP/ICMP Translation Algorithm (SIIT)
·IRIS Traffic Analyzer简易教程
·新的宽带认证方式——IEEE 802.1x协议
·RS-485串行数据通信协议及其应用
·ISIS路由协议

RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1

日期:2007年5月5日 作者: 查看:[大字体 中字体 小字体]



5.1.1 Method

The Method token indicates the method to be performed on the
resource identified by the Request-URI. The method is case-sensitive.

Method = "OPTIONS" ; Section 9.2
"GET" ; Section 9.3
"HEAD" ; Section 9.4
"POST" ; Section 9.5
"PUT" ; Section 9.6
"DELETE" ; Section 9.7
"TRACE" ; Section 9.8
"CONNECT" ; Section 9.9
extension-method
extension-method = token

The list of methods allowed by a resource can be specified in an
Allow header field (section 14.7). The return code of the response
always notifies the client whether a method is currently allowed on a
resource, since the set of allowed methods can change dynamically. An
origin server SHOULD return the status code 405 (Method Not Allowed)
if the method is known by the origin server but not allowed for the
requested resource, and 501 (Not Implemented) if the method is
unrecognized or not implemented by the origin server. The methods GET
and HEAD MUST be supported by all general-purpose servers. All other
methods are OPTIONAL; however, if the above methods are implemented,
they MUST be implemented with the same semantics as those specified
in section 9.

5.1.2 Request-URI

The Request-URI is a Uniform Resource Identifier (section 3.2) and
identifies the resource upon which to apply the request.

Request-URI = "*" absoluteURI abs_path authority

The four options for Request-URI are dependent on the nature of the
request. The asterisk "*" means that the request does not apply to a
particular resource, but to the server itself, and is only allowed
when the method used does not necessarily apply to a resource. One
example would be

OPTIONS * HTTP/1.1

The absoluteURI form is REQUIRED when the request is being made to a
proxy. The proxy is requested to forward the request or service it
from a valid cache, and return the response. Note that the proxy MAY
forward the request on to another proxy or directly to the server

specified by the absoluteURI. In order to avoid request loops, a
proxy MUST be able to recognize all of its server names, including
any aliases, local variations, and the numeric IP address. An example
Request-Line would be:

GET http://www.w3.org/pub/WWW/TheProject.html HTTP/1.1

To allow for transition to absoluteURIs in all requests in future
versions of HTTP, all HTTP/1.1 servers MUST accept the absoluteURI
form in requests, even though HTTP/1.1 clients will only generate
them in requests to proxies.

The authority form is only used by the CONNECT method (section 9.9).

The most common form of Request-URI is that used to identify a
resource on an origin server or gateway. In this case the absolute
path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
the Request-URI, and the network location of the URI (authority) MUST

上一页 [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] [56] [57] [58] [59] [60] [61] [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95] [96] [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108] [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122] [123] [124] [125] [126] [127] [128] [129] [130] [131] 下一页 




上一篇:RFC2617 - HTTP Authentication: Basic and Digest Access Authentication

下一篇:RFC2615 - PPP over SONET/SDH

RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1 相关文章:
·解决与HTTP 500 – 内部服务器错误错误信息有关的问题
·Windows Vista Ultimate中文旗舰版下载+简单破解(支持迅雷HTTP & BT)
·RFC1305 - Network Time Protocol (Version 3) Specification, Implementation
·HTTP500内部服务器错误修正办法
·RFC791 - Internet Protocol
·何谓HTTP 500内部服务器错误
·IE7浏览器访问HTTPS网页故障攻略
·apache配置文件httpd.conf
·Apache2的httpd.conf翻译
·RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1
RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1 相关软件:
·圣斗士冥王篇第五话HTTP高速下载
·获取任意网站数据利器GetHttpData v1.0
·CC File Transfer V2.8
·目前最好的电影程序网狐(http://szfox.com)美化版
·HTTP转SOCKS V1.2
·Port80 Software httpZipv3.6
·宽带HTTP代理服务器[AdslHttpProxy] V1.2
·http://www.skycn.com/soft/4436.html
·Cisco Press CCNP BSCI Configuring IS-IS Protocol
·日语惯用语 来源:http://kenka.ty168.net

特别声明:本站除部分特别声明禁止转载的专稿外的其他文章可以自由转载,但请务必注明出处和原始作者。文章版权归文章原始作者所有。对于被本站转载文章的个人和网站,我们表示深深的谢意。如果本站转载的文章有版权问题请联系编辑人员,我们尽快予以更正。
[打印本页] [关闭窗口] 转载请注明来源:http://www.vipcn.net
| 帮助(?) | 版权声明 | 友情连接 | 关于我们 | 信息发布
Copyright 2007 www.vipcn.net All Rights Reserved. 鄂ICP备05000083号Powered by:viphot