Closed
Bug 1332174
Opened 9 years ago
Closed 9 years ago
Location Bar Search Terms Containing Slashes Not Redirected to Search After NXDOMAIN
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: u564464, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161214035102
Steps to reproduce:
Type a search term containing a forward slash into the location bar, e.g. "test/search" or "Apache/2.2.3 (Red Hat)" without quotes.
Search suggestions in location bar is disabled, as default.
Actual results:
The preview dropdown shows "Search with <Default Provider>" as if it is going to send the typed text as a search query, but when I press enter, it redirects to my ISP's DNS error page, implying that the typed query was incorrectly interpreted and sent as a DNS request instead of a search query.
What is also odd is that this behaviour seems inconsistent; "testdomain/search" was correctly sent as a search when I tested it, but a keyboard mash followed by "/search" was sent as a DNS request.
Expected results:
The typed entries should have been sent to the search engine as a query, not parsed as a domain to be resolved by DNS.
Also, the action listed in the preview dropdown when typing in the location bar should always match the action that is actually being performed when input is entered.
I am unable to reproduce this issue in Windows with the same DNS configuration.
I believe the issue is that in Linux, the query is not getting redirected to the search properly after receiving an NXDOMAIN response from DNS, and instead goes straight to the DNS error resolver page.
Summary: Location Bar Search Terms Containing Slashes are Sent as DNS Requests → Location Bar Search Terms Containing Slashes Not Redirected to Search After NXDOMAIN
Not sure what changed, but this is no longer reproducible in 51.0.1 (64-bit) on the same Linux host. It now reads entries containing a '/' as domains without offering to search for them.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•