New issue
Advanced search Search tips

Issue 626403 link

Starred by 1 user
Status: Duplicate
Merged: issue 344348
Owner: ----
Closed: Jul 2016
Cc:
creis@chromium.org
lukasza@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Setting local search server in omnibox breaks site POST requests.

Reported by j...@apcera.com, Jul 7 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Setup the omnibox to use a local search service at https://127.0.0.1, this would search using a GET.
2. Visit the same search service manually in the browser, fill out a form with action "POST"
3. Notice that chrome now sends a GET instead of the required POST for the form.

What is the expected behavior?
It should post the form since action="post".

What went wrong?
Chrome sends a GET request for a form clearly labelled as a post action.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Last week.

Does this work in other browsers? Yes 

Chrome version: 51.0.2704.106  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by j...@apcera.com, Jul 7 2016 

Also tested this with another site, this is not limited to 127.0.0.1.

You can test this with https://jumps.io.

1. Setup omnibox search provider for jumps. The url is https://jumps.io/search?q=%s
2. Manually go to jumps.io
3. Notice the form now always submits a GET, and not a POST.

Comment 2 by dtapu...@chromium.org, Jul 7 2016

Components: -Blink UI>Browser>Omnibox

Comment 3 by pkasting@chromium.org, Jul 7 2016

Components: -UI>Browser>Omnibox UI>Browser>Navigation UI>Browser>Search
Labels: -Via-Wizard

Comment 4 by mpear...@chromium.org, Jul 7 2016

Labels: Needs-Feedback
Regarding comment #1, jumps.io seems to submit a GET request (as in I see "?q=testing" at the end of the URL) even if I don't have any custom search providers.  Can you confirm that the form actually does submit a GET request _for you_ when you don't have a search provider configured?  In other words, is this actually a problem caused by the search provider mechanism?

Comment 5 by mpear...@chromium.org, Jul 7 2016 

Also note that the recent fix to  bug 344348  might've affected this issue.  It would be nice if you can test it in Chrome Dev or Chrome Canary to see if you can reproduce it there.

thanks!

Comment 6 by creis@chromium.org, Jul 7 2016 

Yes, sounds like this may be a dupe of  issue 344348 .

Comment 7 by creis@chromium.org, Jul 7 2016

Cc: lukasza@chromium.org creis@chromium.org

Comment 8 by mini...@gmail.com, Jul 8 2016 

The URL I sent was what needs to be used for the omnibox. The code works for both post and get requests. When you use the site directly the form is a POST, but chrome translates it to a GET when the omnibox is the same url...

Definitely a bug.

Comment 9 by mini...@gmail.com, Jul 8 2016 

And yes this is a dupe of  issue 344348 . =)

Comment 10 by creis@chromium.org, Jul 8 2016

Mergedinto: 344348
Status: Duplicate (was: Unconfirmed)
Great.  That means it's already fixed in M53.
►

Sign in to add a comment