Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 // Copyright (c) 2011 The Chromium Authors. All rights reserved. | 1 // Copyright (c) 2011 The Chromium Authors. All rights reserved. |
| 2 // Use of this source code is governed by a BSD-style license that can be | 2 // Use of this source code is governed by a BSD-style license that can be |
| 3 // found in the LICENSE file. | 3 // found in the LICENSE file. |
| 4 | 4 |
| 5 #include "net/url_request/url_request.h" | 5 #include "net/url_request/url_request.h" |
| 6 | 6 |
| 7 #include "base/bind.h" | 7 #include "base/bind.h" |
| 8 #include "base/callback.h" | 8 #include "base/callback.h" |
| 9 #include "base/compiler_specific.h" | 9 #include "base/compiler_specific.h" |
| 10 #include "base/memory/singleton.h" | 10 #include "base/memory/singleton.h" |
| (...skipping 677 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 688 } | 688 } |
| 689 | 689 |
| 690 if (!location.is_valid()) | 690 if (!location.is_valid()) |
| 691 return ERR_INVALID_URL; | 691 return ERR_INVALID_URL; |
| 692 | 692 |
| 693 if (!job_->IsSafeRedirect(location)) { | 693 if (!job_->IsSafeRedirect(location)) { |
| 694 DVLOG(1) << "disallowing redirect: unsafe protocol"; | 694 DVLOG(1) << "disallowing redirect: unsafe protocol"; |
| 695 return ERR_UNSAFE_REDIRECT; | 695 return ERR_UNSAFE_REDIRECT; |
| 696 } | 696 } |
| 697 | 697 |
| 698 bool strip_post_specific_headers = false; | 698 // NOTE: Even though RFC 2616 says to preserve the request method when |
| 699 if (http_status_code != 307) { | 699 // following a 302 redirect, normal browsers don't do that. Instead, they |
| 700 // NOTE: Even though RFC 2616 says to preserve the request method when | 700 // all convert a POST into a GET in response to a 302 and so shall we. For |
| 701 // following a 302 redirect, normal browsers don't do that. Instead, they | 701 // 307 redirects, browsers preserve the method. The RFC says to prompt the |
| 702 // all convert a POST into a GET in response to a 302 and so shall we. For | 702 // user to confirm the generation of a new requests, other than GET and HEAD |
| 703 // 307 redirects, browsers preserve the method. The RFC says to prompt the | 703 // requests, but IE omits these prompts and so shall we. |
| 704 // user to confirm the generation of a new POST request, but IE omits this | 704 bool was_post = method_ == "POST"; |
| 705 // prompt and so shall we. | 705 bool rewrite_headers = true; |
|
willchan no longer on Chromium
2011/10/25 15:38:32
Julian Reschke sent me the following comments:
===
mmenke
2011/10/25 16:09:42
I went ahead and did the second, which also allowe
| |
| 706 strip_post_specific_headers = method_ == "POST"; | 706 if (http_status_code == 307) |
| 707 rewrite headers = false; | |
| 708 if ((http_status_code == 301 || http_status_code == 302) && !was_post) | |
| 709 rewrite_headers = false; | |
| 710 if (rewrite_headers) { | |
| 707 method_ = "GET"; | 711 method_ = "GET"; |
| 708 upload_ = NULL; | 712 upload_ = NULL; |
| 713 if (was_post) { | |
| 714 // If being switched from POST to GET, must remove headers that were | |
| 715 // specific to the POST and don't have meaning in GET. For example | |
| 716 // the inclusion of a multipart Content-Type header in GET can cause | |
| 717 // problems with some servers: | |
| 718 // http://code.google.com/p/chromium/issues/detail?id=843 | |
| 719 StripPostSpecificHeaders(&extra_request_headers_); | |
| 720 } | |
| 709 } | 721 } |
| 710 | 722 |
| 711 // Suppress the referrer if we're redirecting out of https. | 723 // Suppress the referrer if we're redirecting out of https. |
| 712 if (GURL(referrer_).SchemeIsSecure() && !location.SchemeIsSecure()) | 724 if (GURL(referrer_).SchemeIsSecure() && !location.SchemeIsSecure()) |
| 713 referrer_.clear(); | 725 referrer_.clear(); |
| 714 | 726 |
| 715 url_chain_.push_back(location); | 727 url_chain_.push_back(location); |
| 716 --redirect_limit_; | 728 --redirect_limit_; |
| 717 | 729 |
| 718 if (strip_post_specific_headers) { | |
| 719 // If being switched from POST to GET, must remove headers that were | |
| 720 // specific to the POST and don't have meaning in GET. For example | |
| 721 // the inclusion of a multipart Content-Type header in GET can cause | |
| 722 // problems with some servers: | |
| 723 // http://code.google.com/p/chromium/issues/detail?id=843 | |
| 724 StripPostSpecificHeaders(&extra_request_headers_); | |
| 725 } | |
| 726 | |
| 727 if (!final_upload_progress_) | 730 if (!final_upload_progress_) |
| 728 final_upload_progress_ = job_->GetUploadProgress(); | 731 final_upload_progress_ = job_->GetUploadProgress(); |
| 729 | 732 |
| 730 PrepareToRestart(); | 733 PrepareToRestart(); |
| 731 Start(); | 734 Start(); |
| 732 return OK; | 735 return OK; |
| 733 } | 736 } |
| 734 | 737 |
| 735 const URLRequestContext* URLRequest::context() const { | 738 const URLRequestContext* URLRequest::context() const { |
| 736 return context_.get(); | 739 return context_.get(); |
| (...skipping 151 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 888 | 891 |
| 889 void URLRequest::SetUnblockedOnDelegate() { | 892 void URLRequest::SetUnblockedOnDelegate() { |
| 890 if (!blocked_on_delegate_) | 893 if (!blocked_on_delegate_) |
| 891 return; | 894 return; |
| 892 blocked_on_delegate_ = false; | 895 blocked_on_delegate_ = false; |
| 893 load_state_param_.clear(); | 896 load_state_param_.clear(); |
| 894 net_log_.EndEvent(NetLog::TYPE_URL_REQUEST_BLOCKED_ON_DELEGATE, NULL); | 897 net_log_.EndEvent(NetLog::TYPE_URL_REQUEST_BLOCKED_ON_DELEGATE, NULL); |
| 895 } | 898 } |
| 896 | 899 |
| 897 } // namespace net | 900 } // namespace net |
| OLD | NEW |