[Pkg-chromium-maint] Bug#749564: chromium uses wrong HTTP method (GET instead of POST) for some URL(s?)
Jason Woofenden
jason at jasonwoof.com
Wed May 28 05:24:45 UTC 2014
Package: chromium
Version: 35.0.1916.114-2
Severity: normal
Dear Maintainer,
I can't for the life of me figure out why chromium won't send a
POST to https://duckduckgo.com/html/
I've made the simplest possible html page/form:
<!DOCTYPE html>
<html>
<head><title></title></head>
<body>
<form action="https://duckduckgo.com/html/" method="post">
<input name="q">
<input type="submit">
</form>
</body>
</html>
If I change the action attribute to any other URL I can think of
(http://jasonwoof.com/, http://google.com/, https://www.paypal.com/, even
https://duckduckgo.com/) it sends a post, but with
https://duckduckgo.com/html/ it sends a GET request.
I tried sites with http, sites with https, sites with HSTS and
without. Everything works (chromium sends a POST) except
https://duckduckgo.com/html/
To reproduce:
1. Paste the above html into a file, and go to it in chromium (or
go to https://duckduckgo.com/html/ and use the form there
(that page has no javascript on it.)
2. right-click anywhere on the page and click "inspect element"
3. click the Network tab
4. check "Preserve log"
5. Type something into the input field and press enter
Note the first entry in the log.
Expected results:
html/ POST 200 ...
Actual results
html/ GET 200
I had this same problem with chromium 34.whatever that was in sid
until very recently.
I've disabled all my plugins, restarted chromium, and I'm not using
a proxy of any kind. I do _not_ have "Enable phishing and malware
protection" checked in the chromium settings.
This is very frustrating. I've got ddg/html/ as my default search
engine (using GET) but if I edit the search terms in the ddg form,
it doesn't send the form fields (it sends a GET (as described
above) without any query string.) I suppose I could work around
this with a tampermonkey script to change the ddg forms to
method="GET", but it seems to me something is seriously wrong here,
so I made this bug report.
I hope that's helpful.
Please let me know if I can help with further testing/etc.
Thank you!
--
Jason
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 35.0.1916.114-2
ii gconf-service 3.2.6-2
ii libasound2 1.0.27.2-4
ii libc6 2.18-7
ii libcairo2 1.12.16-2
ii libcap2 1:2.22-1.2
ii libcups2 1.7.2-3
ii libdbus-1-3 1.8.2-1
ii libexpat1 2.1.0-5
ii libfontconfig1 2.11.0-5
ii libfreetype6 2.5.2-1
ii libgcc1 1:4.9.0-4
ii libgconf-2-4 3.2.6-2
ii libgcrypt11 1.5.3-4
ii libgdk-pixbuf2.0-0 2.30.7-1
ii libglib2.0-0 2.40.0-3
ii libgnome-keyring0 3.8.0-2
ii libgtk2.0-0 2.24.23-1
ii libharfbuzz0b 0.9.28-2
ii libjpeg8 8d-2
ii libnspr4 2:4.10.4-1
ii libnss3 2:3.16-1
ii libpango-1.0-0 1.36.3-1
ii libpangocairo-1.0-0 1.36.3-1
ii libspeechd2 0.8-6
ii libspeex1 1.2~rc1.1-1
ii libstdc++6 4.9.0-4
ii libudev1 204-10
ii libx11-6 2:1.6.2-2
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1
ii libxdamage1 1:1.1.4-1
ii libxext6 2:1.3.2-1
ii libxfixes3 1:5.0.1-1
ii libxi6 2:1.7.2-1
ii libxml2 2.9.1+dfsg1-3
ii libxrandr2 2:1.4.2-1
ii libxrender1 1:0.9.8-1
ii libxslt1.1 1.1.28-2
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-7.1
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
pn mozplugger <none>
-- no debconf information
More information about the Pkg-chromium-maint
mailing list