Closed Bug 207269 Opened 22 years ago Closed 19 years ago

long lines of text are broken when mail is sent via form submission.

Categories

(MailNews Core :: MIME, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kelly, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 When using a form mailto: from mozilla with the enctype="application/x-www-form-urlencoded", if the encoded form data is long enough, it is broken at points, but these breaks are not reflected in the original content of the body text when the user clicks "send". Reproducible: Always Steps to Reproduce: 1. create a form with the action="mailto:name@server.org" (optional: explicitly set enctype="application/x-www-form-url-encoded"). 2. submit the form and examine the email message prepared for submission. There are no line breaks in the message, just one line of a large CGI-encoded string to represent your form data. 3. send the email. Actual Results: Look in your sent folder and see that the message that was sent has line breaks inserted into it. It can also be verified with word-wrap turned off on the received message that it indeed does break the CGI string with line breaks. Expected Results: CGI strings should not be broken with linebreaks or carraige returns. This poses a problem as data should not be modified during submission for ANY MIME "application" type, but any method submitted (including "application/octet-stream") will insert these linefeeds into the submitted message. Alternatively, maybe when the data is submitted as type "application/*" it should be generated as an attachment instead of body content? Maybe this is a problem with the interpretation of data submitted by the browser?
Product: MailNews → Core
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
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.