Bug 274167

Summary: Doubled HTTP requests with Konqueror
Product: [Applications] konqueror Reporter: Neil Skrypuch <kde>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 4.6.3   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Neil Skrypuch 2011-05-26 06:17:34 UTC 
Version:           4.6.3 (using KDE 4.6.3) 
OS:                Linux

When browsing with Konqueror, the main HTTP request for that page (basically, what you see in the URL bar) is made twice. This happens for both GET and POST requests.

Notably, AJAX requests are NOT doubled, only regular requests. In addition, images on the page, external Javascript, stylesheets, etc, do not appear to be double loaded unless they are navigated to directly.

Reproducible: Always

Steps to Reproduce:
1. Open any webpage in Konqueror
2. Observe doubled HTTP request

Actual Results:  
Main HTTP request for the webpage is performed twice.

Expected Results:  
Main HTTP request for the webpage is performed only once.

In general usage, this bug is often difficult to notice. However, due to the fact that this also affects POST requests, the consequences can be quite bad. Double posting in forums, double sending emails, double buying things online... Even this bug report will probably get filed twice, as I'm filing it with Konqueror 4.6.3, note that I personally only filed it once.

Previously I was using 4.6.1 and I never observed this bug there. I skipped 4.6.2, so I'm not sure if it was present there, but it was definitely a regression somewhere between 4.6.1 and 4.6.3.

This is probably easiest to observe if you hit a server for which you're watching the logs, but you could probably tcpdump the traffic as well.
Comment 1 Neil Skrypuch 2011-05-26 06:22:15 UTC 
Luckily, Bugzilla appears to have protection against replay attacks, so the bug was only filed once. However, I never got to see the "bug filed successfully" screen, all I got was a warning that the form had already been used to file this bug. Anyways, one additional point I forgot to mention is that the second request is the one that's actually displayed in the browser, not the first one. It's not usually clear whether the first or the second request is being displayed, but in cases where it is clear, it has always been the second request, never the first.
Comment 2 Tommi Tervo 2011-05-26 08:16:46 UTC 

*** This bug has been marked as a duplicate of bug 272466 ***