RESOLVED FIXED Bug 112194
REGRESSION(r137607): Redirecting a post to a get then reloading triggers resubmit warning
https://bugs.webkit.org/show_bug.cgi?id=112194
Summary REGRESSION(r137607): Redirecting a post to a get then reloading triggers resu...
Nate Chapin
Reported 2013-03-12 15:04:45 PDT
Original report: https://code.google.com/p/chromium/issues/detail?id=177855 From the original bug: UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Ubuntu Chromium/24.0.1312.56 Chrome/24.0.1312.56 Safari/537.17 Example URL: http://demo.sperke.net/postredirect.php Steps to reproduce the problem: 1. Open the link 2. Click the submit button 3. Your request will be sent and you are redirected with header code 303 to the same url 4. Hit the reload button What is the expected behavior? The page should reload. What went wrong? Chrome asks for resubmitting the form. That is wrong because the last request was a get and no post request. The values should not be resent.
Attachments
patch (5.44 KB, patch)
2013-03-12 15:10 PDT, Nate Chapin
no flags
Checking build fix on EWS (5.64 KB, patch)
2013-03-13 09:36 PDT, Nate Chapin
gtk-ews: commit-queue-
another ews experiment (7.16 KB, patch)
2013-03-13 10:28 PDT, Nate Chapin
no flags
Patch for landing (8.41 KB, patch)
2013-03-13 11:48 PDT, Nate Chapin
no flags
Nate Chapin
Comment 1 2013-03-12 15:10:32 PDT
Alexey Proskuryakov
Comment 2 2013-03-12 15:42:09 PDT
Comment on attachment 192820 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=192820&action=review > Source/WebCore/loader/SubresourceLoader.cpp:135 > + if (!redirectResponse.isNull()) { How can SubresourceLoader::willSendRequest be called with a null redirectResponse? Could you please post a stack trace?
Nate Chapin
Comment 3 2013-03-12 15:51:28 PDT
(In reply to comment #2) > (From update of attachment 192820 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=192820&action=review > > > Source/WebCore/loader/SubresourceLoader.cpp:135 > > + if (!redirectResponse.isNull()) { > > How can SubresourceLoader::willSendRequest be called with a null redirectResponse? Could you please post a stack trace? It's called for the initial request from ResourceLoader::init(). For example: STDERR: [0x0000008ec390] WebCore::SubresourceLoader::willSendRequest() STDERR: [0x0000008e6b17] WebCore::ResourceLoader::init() STDERR: [0x0000008ec1fa] WebCore::SubresourceLoader::init() STDERR: [0x0000008ec09f] WebCore::SubresourceLoader::create() STDERR: [0x000000c2aec8] WebCore::ResourceLoadScheduler::scheduleSubresourceLoad() STDERR: [0x000000908ba7] WebCore::CachedResource::load() STDERR: [0x000000915b02] WebCore::CachedResourceLoader::requestResource() STDERR: [0x000000914e72] WebCore::CachedResourceLoader::requestMainResource() STDERR: [0x0000008db8dc] WebCore::MainResourceLoader::load() STDERR: [0x0000008a5939] WebCore::DocumentLoader::startLoadingMainResource()
Build Bot
Comment 4 2013-03-13 04:58:58 PDT
Nate Chapin
Comment 5 2013-03-13 09:36:13 PDT
Created attachment 192937 [details] Checking build fix on EWS
kov's GTK+ EWS bot
Comment 6 2013-03-13 09:56:08 PDT
Comment on attachment 192937 [details] Checking build fix on EWS Attachment 192937 [details] did not pass gtk-ews (gtk): Output: http://webkit-commit-queue.appspot.com/results/17133064
Build Bot
Comment 7 2013-03-13 10:10:37 PDT
Comment on attachment 192937 [details] Checking build fix on EWS Attachment 192937 [details] did not pass win-ews (win): Output: http://webkit-commit-queue.appspot.com/results/17178331
Nate Chapin
Comment 8 2013-03-13 10:28:18 PDT
Created attachment 192944 [details] another ews experiment
Nate Chapin
Comment 9 2013-03-13 11:48:35 PDT
Created attachment 192955 [details] Patch for landing
WebKit Review Bot
Comment 10 2013-03-13 12:16:47 PDT
Comment on attachment 192955 [details] Patch for landing Clearing flags on attachment: 192955 Committed r145735: <http://trac.webkit.org/changeset/145735>
WebKit Review Bot
Comment 11 2013-03-13 12:16:52 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.