Closed Bug 58397 Opened 24 years ago Closed 23 years ago

POST submission sends extra \n when submitting data to other webserver than apache.

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED WORKSFORME
Future

People

(Reporter: tobi, Assigned: pollmann)

References

()

Details

While working on a cgi script under Roxen webserver I discovered that I got an
extra \n in my POST submission and I thought it was a problem with roxen but
trying the site out in an other browser show that it works. Apperently mozilla
sends \n\r\n instead of \n\r as a end to POST submissions (or something)
Reporter, is this still an issue with the latest build
(http://ftp.mozilla.org/pub/mozilla/nightly)? Also please make a query in
bugzilla and see if you can find a duplicate, it sounds familiar. Please provide
the buildID with which you test(ed) this.
Thank you!
Fabian.
reassigning
Assignee: rods → pollmann
Hm, pretty sure we send \r\n as the final characters - it would be quite strange
if a browser was ending with \n\r since the network linebreak character is \r\n.
 Can you provide information such as what platform you are running the client
web browser on (Mac, Windows, Un*x) and what platform you are running the web
server on?  Also, what method are you using to grab the raw data sent to the web
server?


Relevant code in nsFormFrame.cpp (line 1188, in ProcessAsURLEncoded):
  aData += buf;
  // Need to append CRLF to end of stream for compatability with Nav and IE
  if (isPost) {
    aData.AppendWithConversion(CRLF);
  }
Here are some more information. The client platform is Linux 2.2.17 debian 2.3
and the mozilla I am using has build id: 2000120808 and the server platform is
FreeBSD 4.0 with roxen webserver 2.0. You can check it out at :
http://www.debian.as/home/tobi/testmoz.html in both netscape and mozilla to see
the diffrence. 
I am going to mark this NEW, since i see it as well as the fact it may or may
not be unintentional. Can someone please look at this and if were not going to
fix it mark it as WONTFIX or INVALID.
Status: UNCONFIRMED → NEW
Ever confirmed: true
tobi@tobi.nu, do you still see this behavior with the nightlies?
i was unable to duplicate it with 2001010904 on winNT,
2001010909 on Solaris or 2001011021 on i686-pc-linux.

verified the correct (CRLF) behavior with an octal dump from netcat,
which showed the final two characters as 0d 0a (as expected)
per previous comment: WORKSFORME
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Target Milestone: --- → Future
verifying per hugh's comments.
Status: RESOLVED → VERIFIED
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.