302 Found 是HTTP協議中的一個狀態碼(Status Code)，可以簡單的理解為該資源原本確實存在，但已經被臨時改變了位置；或者換個說法，就是臨時的存在於某個臨時URL下。通常會發送Header來暫時重定向到新的新位置。 官方給出的英語解釋為： The 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。
302 Found 是HTTP協議中的一個狀態碼(Status Code)，可以簡單的理解為該資源原本確實存在，但已經被臨時改變了位置；或者換個說法，就是臨時的存在於某個臨時URL下。通常會發送Header來暫時重定向到新的新位置。 官方給出的英語解釋為： The 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。