use of hexa encoded mailto give wrong results : subject fields are not understood.

RESOLVED INVALID

Status

SeaMonkey
General
RESOLVED INVALID
14 years ago
13 years ago

People

(Reporter: cyrano, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030428

If i encode mail string with :
http://www.neokraft.net/sottises/mailencoder/

mailto:sympa@toto.org?subject=subscribe%20test became : 
mailto:%73%79%6d%70%61%40%74%6f%74%6f%2e%6f%72%67%3f%73%75%62%6a%65%63%74%3d%73%75%62%73%63%72%69%62%65%25%32%30%74%65%73%74

This could be used to defeat spam robot.

but mozilla open the mailer with :
sympa@toto.org?subject=subscribe%20test
as e-mail adress instead of filling the subject fields.


Reproducible: Always
Steps to Reproduce:
1. encode a mail adresse in hexa 
2. use a mailto: link
3. clic on it

Actual Results:  
all the text goes to "to:" fields

Expected Results:  
dispatch data to "to:" and "subject:"
The '?' char separates the mail address from the fields.  But if it's encoded,
it loses its special meaning, like all special chars in urls.  Otherwise, how
could you put a '?' into the address?

So our behavior is correct.  In the same way, if you escape:

http://foo.com/bar

the '/' after foo.com loses its special meaning and the hostname becomes
"foo.com/bar".

The only bug I see here is in the software that blindly escapes every single
char in the URL.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

14 years ago
ok, i understand the behavior of special character : "?"  and "=" but why "subject" can't 
be also hexa encoded ? 
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.