用户
 找回密码
 入住 CI 中国社区
搜索
楼主: szq
收起左侧

[讨论/交流] 作为新人,我也在这里开一帖,见证我的学习历程以及督促

    [复制链接]
 楼主| 发表于 2012-7-9 11:24:58 | 显示全部楼层
今天在练习类库中购物车类cart的时候出现了两个问题,查了相关资料后,总算解决了,暗喜中.......

原理:购物车类允许项目被添加到session中,session在用户浏览你的网站期间都保持有效状态。这些项目能够以标准的 "购物车" 格式被检索和显示,并允许用户更新数量或者从购物车中移除项目。请注意购物车类只提供核心的"购物车"功能。它不提供配送、信用卡授权或者其它处理组件。重要:购物车类利用 CodeIgniter 的 Session 类把购物车信息保存到数据库中,所以在使用购物车类之前,你必须根据 Session 类文档中的说明来创建数据库表,并且在 application/config/config.php 文件中把 Session 相关参数设置为使用数据库
购物车类载入方式:$this->load->library['cart'];
调用方式:$this->cart
数据载入方式:以一维(单件商品)或多维(多件商品)的方式插入,如:
$data = array(
               array(
                       'id'      => 'sku_123ABC',
                       'qty'     => 1,
                       'price'   => 39.95,
                       'name'    => 'T-Shirt',
                       'options' => array('Size' => 'L', 'Color' => 'Red')
                    ),
               array(
                       'id'      => 'sku_567ZYX',
                       'qty'     => 1,
                       'price'   => 9.95,
                       'name'    => 'Coffee Mug'
                    ),
               array(
                       'id'      => 'sku_965QRS',
                       'qty'     => 1,
                       'price'   => 29.95,
                       'name'    => 'Shot Glass'
                    )
            );

$this->cart->insert($data);

重要说明: 上面的前四个数组索引 (id, qty, price 和name) 是 必需的。如果缺少其中的任何一个,数据将不会被保存到购物车中。第5个索引 (options) 是可选的。当你的商品包含一些相关的选项信息时,你就可以使用它。正如上面所显示的那样,请使用一个数组来保存选项信息。注意:$data['price'] 的值必须大于0

在练习过程中遇到的问题如下
问题一:错误提示“An Error Was Encountered
In order to use the Session class you are required to set an encryption key in your config file.”
解决办法:在项目文件夹里找到application/config/config.php里找到$config['encryption_key'] = '';在其后加入任何字符串即可解决错误,如$config['encryption_key']='szq'等

问题二:错误提示如下:
A Database Error OccurredError Number: 1146
Table 'test.ci_sessions' doesn't exist
SELECT * FROM (`ci_sessions`) WHERE `session_id` = 'b3ea233b915ac4f87f3ed0954753b85f' AND `user_agent` = 'Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)'
Filename: D:\wamp\www\ci_study\system\database\DB_driver.php
Line Number: 330
问题所在及解决办法:在执行数据插入之前没有建立"ci_sessions"表,查看了手册,根据代码
SQL复制代码
CREATE TABLE IF NOT EXISTS  `ci_sessions` (
session_id VARCHAR(40) DEFAULT '0' NOT NULL,
ip_address VARCHAR(16) DEFAULT '0' NOT NULL,
user_agent VARCHAR(50) NOT NULL,
last_activity INT(10) UNSIGNED DEFAULT 0 NOT NULL,
user_data text DEFAULT '' NOT NULL,
PRIMARY KEY (session_id)
);
复制代码
之后,问题得以解决。

自己一天天的在进步,感觉每一天都很充实,但愿自己能一直这样“锲而不舍,金石可缕”.



 楼主| 发表于 2012-7-10 09:35:06 | 显示全部楼层
“绳锯木断,滴水穿石”-------------开始新的一天的学习。
昨天联系ci类库email类的时候,按照手册,查看网络资料,整个配置下来发不了邮件,不知道是什么问题,有遇到过类似问题,但解决了相关问题的朋友给个帮助吧。
 楼主| 发表于 2012-7-10 15:55:32 | 显示全部楼层
再留一脚,邮件问题解决了,感到有点小成就感。

发送邮件
发送邮件不仅简单,而且可以发送时进行配置或者将参数放到配置文件中。

这里是一个发送邮件的标准示例。注意:该示例是假定使用一个控制器来发送邮件。

$this->load->library('email');

$this->email->from('your@example.com', 'Your Name');
$this->email->to('someone@example.com');
$this->email->cc('another@another-example.com');
$this->email->bcc('them@their-example.com');

$this->email->subject('Email Test');
$this->email->message('Testing the email class.');

$this->email->send();

echo $this->email->print_debugger();

设置 Email 参数
有17个不同的有效参数来提供给你如何定制你发送的电子邮件。您可以在此手动设置,或自动通过你储存在的配置文件中的来设置,描述如下:

参数设定通过一系列的参数值去完成电子邮件的initialize功能。这里有一个例子,说明怎样设置一些参数设定:

$config['protocol'] = 'sendmail';
$config['mailpath'] = '/usr/sbin/sendmail';
$config['charset'] = 'iso-8859-1';
$config['wordwrap'] = TRUE;

$this->email->initialize($config);

说明: 大多数参数都有默认值,如果你没有配置这些参数,它们的默认值就会被使用。

在配置文件中设置 Email 参数
如果您不想使用使用上述方法设定参数,您可以把它们放入一个配置文件。创建一个新文件称为email.php ,添加$config数组在该文件中。然后将该文件保存为config/email.php 它将自动的被使用。如果您保存了一个参数配置文件,就不需要使用$this->email->initialize()函数来初始化参数了

Email 参数
下面是发送电子邮件时可以设置的属性的列表。

参数 默认值 选项 描述
useragent CodeIgniter 无 用户代理 "user agent"。
protocol mail mail, sendmail, or smtp 邮件发送协议。
mailpath /usr/sbin/sendmail 无 服务器上 Sendmail 的实际路径。protocol 为 sendmail 时使用。
smtp_host 无默认值 无 SMTP 服务器地址。
smtp_user 无默认值 无 SMTP 用户账号。
smtp_pass 无默认值 无 SMTP 密码。
smtp_port 25 无 SMTP 端口。
smtp_timeout 5 无 SMTP 超时设置(单位:秒)。
wordwrap TRUE TRUE 或 FALSE (布尔值) 开启自动换行。
wrapchars 76  自动换行时每行的最大字符数。
mailtype text text 或 html 邮件类型。发送 HTML 邮件比如是完整的网页。请确认网页中是否有相对路径的链接和图片地址,它们在邮件中不能正确显示。
charset utf-8  字符集(utf-8, iso-8859-1 等)。
validate FALSE TRUE 或 FALSE (布尔值) 是否验证邮件地址。
priority 3 1, 2, 3, 4, 5 Email 优先级. 1 = 最高. 5 = 最低. 3 = 正常.
crlf \n "\r\n" or "\n" or "\r" 换行符. (使用 "\r\n" to 以遵守RFC 822).
newline \n "\r\n" or "\n" or "\r" 换行符. (使用 "\r\n" to 以遵守RFC 822).
bcc_batch_mode FALSE TRUE or FALSE (boolean) 启用批量暗送模式.
bcc_batch_size 200 None 批量暗送的邮件数.

Email 函数参考
$this->email->from()
设置发件人email地址和名称:

$this->email->from('you@example.com', 'Your Name');

$this->email->reply_to()
设置邮件回复地址. 如果没有提供这个信息,将会使用"from()"函数中的值. 例如:

$this->email->reply_to('you@example.com', 'Your Name');

$this->email->to()
设置收件人email地址(多个). 地址可以是单个、一个以逗号分隔的列表或是一个数组:

$this->email->to('someone@example.com');

$this->email->to('one@example.com, http://example.com/a_long_link_that_should_not_be_wrapped.html{/unwrap}

More text that will be
wrapped normally.

将你不想自动换行的部分放入: {unwrap} {/unwrap}中间
 楼主| 发表于 2012-7-11 17:51:34 | 显示全部楼层
今天的文件上传和表单验证很顺利,暗喜中
发表于 2012-7-14 14:00:58 | 显示全部楼层
发表于 2012-7-14 16:30:48 | 显示全部楼层
每天进步一点点……
 楼主| 发表于 2012-7-16 11:55:00 | 显示全部楼层
新的一周开始了,先报个到,框架手册内容过了一遍,打算过段时间自己做个小项目练练手......
 楼主| 发表于 2012-7-16 12:01:30 | 显示全部楼层
header头部信息详细解析:
part of Hypertext Transfer Protocol -- HTTP/1.1
RFC 2616 Fielding, et al.[url=]10[/url] Status Code DefinitionsEach Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response.
[url=]10.1[/url] Informational 1xxThis class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions.
A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent.
Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a
proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).)
[url=]10.1.1[/url] 100 ContinueThe client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code.
[url=]10.1.2[/url] 101 Switching ProtocolsThe server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.
[url=]10.2[/url] Successful 2xxThis class of status code indicates that the client's request was successfully received, understood, and accepted.
[url=]10.2.1[/url] 200 OKThe request has succeeded. The information returned with the response is dependent on the method used in the request, for example:
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
[url=]10.2.2[/url] 201 CreatedThe request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead.
A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, see section 14.19.
[url=]10.2.3[/url] 202 AcceptedThe request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.
The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.
[url=]10.2.4[/url] 203 Non-Authoritative InformationThe returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).
[url=]10.2.5[/url] 204 No ContentThe server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.
If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view.
The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.
[url=]10.2.6[/url] 205 Reset ContentThe server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
[url=]10.2.7[/url] 206 Partial ContentThe server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field (section 14.35) indicating the desired range, and MAY have included an If-Range header field (section 14.27) to make the request conditional.
The response MUST include the following header fields:
      - Either a Content-Range header field (section 14.16) indicating        the range included with this response, or a multipart/byteranges        Content-Type including Content-Range fields for each part. If a        Content-Length header field is present in the response, its        value MUST match the actual number of OCTETs transmitted in the        message-body.      - Date      - ETag and/or Content-Location, if the header would have been sent        in a 200 response to the same request      - Expires, Cache-Control, and/or Vary, if the field-value might        differ from that sent in any previous response for the same        variantIf the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
A cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see 13.5.4.
A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.
[url=]10.3[/url] Redirection 3xxThis class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection.
      Note: previous versions of this specification recommended a      maximum of five redirections. Content developers should be aware      that there might be clients that implement such a fixed      limitation.[url=]10.3.1[/url] 300 Multiple ChoicesThe requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content- Type header field. Depending upon the format and the capabilities of
the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.
If the server has a preferred choice of representation, it SHOULD include the specific URI for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
[url=]10.3.2[/url] 301 Moved PermanentlyThe requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
      Note: When automatically redirecting a POST request after      receiving a 301 status code, some existing HTTP/1.0 user agents      will erroneously change it into a GET request.[url=]10.3.3[/url] 302 FoundThe requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
      Note: RFC 1945 and RFC 2068 specify that the client is not allowed      to change the method on the redirected request.  However, most      existing user agent implementations treat 302 as if it were a 303      response, performing a GET on the Location field-value regardless      of the original request method. The status codes 303 and 307 have      been added for servers that wish to make unambiguously clear which      kind of reaction is expected of the client.[url=]10.3.4[/url] 303 See OtherThe response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.
The different URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
      Note: Many pre-HTTP/1.1 user agents do not understand the 303      status. When interoperability with such clients is a concern, the      302 status code may be used instead, since most user agents react      to a 302 response as described here for 303.[url=]10.3.5[/url] 304 Not ModifiedIf the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.
The response MUST include the following header fields:
      - Date, unless its omission is required by section 14.18.1If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], section 14.19), caches will operate correctly.
      - ETag and/or Content-Location, if the header would have been sent        in a 200 response to the same request      - Expires, Cache-Control, and/or Vary, if the field-value might        differ from that sent in any previous response for the same        variantIf the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.
If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.
[url=]10.3.6[/url] 305 Use ProxyThe requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.
      Note: RFC 2068 was not clear that 305 was intended to redirect a      single request, and to be generated by origin servers only.  Not      observing these limitations has significant security consequences.[url=]10.3.7[/url] 306 (Unused)The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.
[url=]10.3.8[/url] 307 Temporary RedirectThe requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.
If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
[url=]10.4[/url] Client Error 4xxThe 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user.
If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted by the HTTP application.
[url=]10.4.1[/url] 400 Bad RequestThe request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
[url=]10.4.2[/url] 401 UnauthorizedThe request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].
[url=]10.4.3[/url] 402 Payment RequiredThis code is reserved for future use.
[url=]10.4.4[/url] 403 ForbiddenThe server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
[url=]10.4.5[/url] 404 Not FoundThe server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
[url=]10.4.6[/url] 405 Method Not AllowedThe method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
[url=]10.4.7[/url] 406 Not AcceptableThe resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.
      Note: HTTP/1.1 servers are allowed to return responses which are      not acceptable according to the accept headers sent in the      request. In some cases, this may even be preferable to sending a      406 response. User agents are encouraged to inspect the headers of      an incoming response to determine if it is acceptable.If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.
[url=]10.4.8[/url] 407 Proxy Authentication RequiredThis code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field (section 14.33) containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field (section 14.34). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].
[url=]10.4.9[/url] 408 Request TimeoutThe client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
[url=]10.4.10[/url] 409 ConflictThe request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough
information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type.
[url=]10.4.11[/url] 410 GoneThe requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the server owner.
[url=]10.4.12[/url] 411 Length RequiredThe server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
[url=]10.4.13[/url] 412 Precondition FailedThe precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
[url=]10.4.14[/url] 413 Request Entity Too LargeThe server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again.
[url=]10.4.15[/url] 414 Request-URI Too LongThe server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.
[url=]10.4.16[/url] 415 Unsupported Media TypeThe server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
[url=]10.4.17[/url] 416 Requested Range Not SatisfiableA server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)
When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). This response MUST NOT use the multipart/byteranges content- type.
[url=]10.4.18[/url] 417 Expectation FailedThe expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
[url=]10.5[/url] Server Error 5xxResponse status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.
[url=]10.5.1[/url] 500 Internal Server ErrorThe server encountered an unexpected condition which prevented it from fulfilling the request.
[url=]10.5.2[/url] 501 Not ImplementedThe server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
[url=]10.5.3[/url] 502 Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
[url=]10.5.4[/url] 503 Service UnavailableThe server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
      Note: The existence of the 503 status code does not imply that a      server must use it when becoming overloaded. Some servers may wish      to simply refuse the connection.[url=]10.5.5[/url] 504 Gateway TimeoutThe server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
      Note: Note to implementors: some deployed proxies are known to      return 400 or 500 when DNS lookups time out.[url=]10.5.6[/url] 505 HTTP Version Not SupportedThe server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in section 3.1, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.


发表于 2012-7-16 14:39:06 | 显示全部楼层
贵在持之以恒
 楼主| 发表于 2012-7-17 11:46:03 | 显示全部楼层
今天想写个小东西,用到框架前面的知识,大脑一片空白,当时差点泪奔,辛辛苦苦学的东西,怎么忘了呢,边学边忘呀........
还是练习不够多,实践不够多,还是要加大实践的时间比例!

本版积分规则