limit keyword functions to user-entered data

RESOLVED EXPIRED

Status

()

--
minor
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: sazgcwzkwy, Assigned: bugs)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
Right now, if I have a webpage containing a 
form with action set to 
https://http//mail.yahoo.com
(assuming the site author didn't notice the typo)
it will actually post the contents of the form
to microsoft.com site. In this particular example,
we can probably assume microsoft wouldn't want
to collect such unwanted data, but it is still 
a risk. 

Shouldn't the "automatic I-am-feeling-lucky type
searches" be limited to only those typed-in
explicitly by the user.

I confirmed this in the 
latest firefox nightly build. Tested
on Windows, FreeBSD, and Linux

I really enjoy using Firefox.
Thanks for all your effort.

Comment 1

14 years ago

*** This bug has been marked as a duplicate of 231720 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → DUPLICATE
Nope, not a dup of bug 231720, where mconnor's INVA was based on "you type weird
things in the address bar, you get weird results." Even though comment 0 is
wrong about the data being POSTed (or even GETted), near as I can tell, there's
no benefit whatsoever to doing fixup on a form action, and even if there's no
risk, it looks awful.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---

Updated

14 years ago
Summary: Explicit HREF links should not use Search feature (Security risk) → limit keyword functions to user-entered data
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.