When following a 307 redirect, XmlHttpRequest incorrectly changes the HTTP method to "GET".
How to test: - Start browser. - Open link provided under URL in this bug report. - Should give you one alert at the start of page loading, "if your browser asks you permission to follow a redirect, please allow it". - OK that alert plus any following ones abour redirects (I think only FF asks about the redirects). This particular bug report is about the section "Redirects" of the test page, although there are some failures before the 307 redirect that the report refers to. Here are the results for numbers 16-20 which relate to 307 redirects. Results in Firefox 12: 307 Temporary Redirect, POST: success 307 Temporary Redirect, GET: success 307 Temporary Redirect, HEAD: success 307 Temporary Redirect, PUT: success 307 Temporary Redirect, DELETE: success Results in Konqueror from KDE 4.7.2: 307 Temporary Redirect, POST: success 307 Temporary Redirect, GET: success 307 Temporary Redirect, HEAD: success 307 Temporary Redirect, PUT: success 307 Temporary Redirect, DELETE: fail (Test execution problem: expected response header field ('x-method') missing.) In 4.7.2, loading the page takes a long (looooong) time, as it chokes at 79% (item 8, method FOO) for a minute or more. Given that newer Konquerors implement at least the 307-redirect method preservation that the OP asks for, I think this bug can be closed. (Of course, a follow-up bug would be that Konqueror doesn't properly ask for permission when dealing with redirects, and some of the other failures on that test page).
For completeness: in KDE 4.4.4, the results of tests 16-20 in Redirect are: 307 Temporary Redirect, POST: fail (Redirected using GET, expected POST) 307 Temporary Redirect, GET: success 307 Temporary Redirect, HEAD: fail (Redirected using GET, expected HEAD) 307 Temporary Redirect, PUT: fail (Redirected using GET, expected PUT) 307 Temporary Redirect, DELETE: fail (Redirected using GET, expected DELETE) In 4.4.4 the failure to ask about redirects was aalso lready there.
> In 4.7.2, loading the page takes a long (looooong) time, as it chokes at 79% (item 8, method FOO) for a minute or more. For me it chokes completely (have been waiting for over 5 minutes now). This probably deserves a second bug.