152498 - multipart/form-data boundary delimiter consistency issues.

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Dan Goehring]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    2002051006

With Mozilla, when transferring a file using "forms" and 
enctype="multipart/form-data", the first time I do it, the boundary delimiter 
is correct for the start and end of the content being transferred.  When 
transferring the same file again within the same TCP connection, the boundary 
delimiter sent before the start of the file is correct, but the boundary 
delimiter following the end of the file is incorrect.  It is making it 
difficult for my server to determine the end of the file it is receiving.  It 
appears that Mozilla is sending a different boundary delimiter for some 
reason.  If I close the TCP connection and restart it, the above repeats itself.

Reproducible: Always
Steps to Reproduce:
1.Using "forms" and enctype="multipart/form-data", send a text file of 30,000 
bytes or so.  Take note of the boundary delimiter that is sent before and after 
the file transfer.
2.Within the same TCP connection, send the same file again and take note of the 
boundary delimiter that is sent before and after the file transfer.  For me, 
the boundary delimiter following the file transfer is not correct.
3.

Actual Results:  The second time while sending the file in the same TCP/IP 
connection, the boundary delimiter sent following the ascii text file is not 
correct.
For example it might supposed to look like this...
---------------------------4664151417711--
But instead it ends up changed, for example it could look like this...
---------------------------9119368323864-- (This number was made up).


Expected Results:  With a boundary delimiter of...
---------------------------4664151417711--

I expect to see... 
---------------------------4664151417711--

before and after the ascii file being transferred all the time.

The server Mozilla is talking to is home-brew, but it shouldn't matter because 
I'm dumping TCP packet contents and observing what is being transferred.

Comment 1

[Dan Goehring]

After some more debugging I'm pretty sure this is a windows problem - Not 
Mozilla's.  Using trace dump, the TCP stream just appears to stop.  I have no 
idea why the ethernet packets just stop transmitting from the windows 
computer.  Rebooting seems to fix the problem.