Closed
Bug 456936
Opened 17 years ago
Closed 17 years ago
Firefox doesn't send first KBytes of the file when uploading it to (any) server
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 463579
People
(Reporter: stefan.ludwig, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.2) Gecko/2008091620 Firefox/3.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.2) Gecko/2008091620 Firefox/3.0.2
I performed an formular (POST) upload to an embedded system (I tested also an upload on an Apache Server with php5) with a text file of 3.2 MB and found following behaviour:
The first data sent by the Firefox is about line 40 of the file - obviously also some information about the file sent is ommited, so that the receiver is not able to figure out the filename.
Is anyone able to confirm this behaviour with this Firefox version (3.0.1 and 3.0.2)? (With older versions 2.x it works - and I didn't test it with 3.0.0)
The file test.txt start with these lines (its a text (srecord) file):
S00600004844521B
S32500000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF567FFF02001C633800567FFF02001C6308
.
.
.
S325000004C0141F4141F4141F4141F4141C41000000000344F4444F4444F4444C4400000333FF
S325000004E0F3333F3337F3737D3745444400000115117145F4545F4545F4545C45000345F40D
S32500000500545F4545F4545F4545F4545C45000000023A33B374F7474F7444F4444C4401E5F5
S32500000520EE7ECBFCBCBCCB0000013533537577574544440000021A11B154F5454F5444F42C
S32500000540444C44000354F5454F5454F5454F5454F5454C54000000021A11B154F5454F541F
S3250000056044F4444C4400000323F2323F23A6FA6A6FA684F8484C8400000311F1111F11556F
S32500000580F5555F5545F4545C45000355F5555F5555F5555F5555F5555C55000000012522E8
S325000005A05265665645444400000331F3131F31F8FF8F8FF8C8FC8C8CC8000001151151152D
S325000005C0115115114100011511511511511511410000000312F1212F1252F5252E524A4414
S325000005E08400021A11B121F2121F21ACFACACFAC8CBBBBBBBBBBBBBBBBB5227211F1111F1A
S325000006001153F5353F5343F4343D4325225225227253F5353F5353F5353F5353F5353C534D
S325000006200000000332F3232F3276F7676F7644F4444C440000013533738EF8E8EF8E8CF8F8
S32500000640C8CC8C0125225225227221F2121F2167F6767F6747F4747D4725225225227267D7
S32500000660F6767F6767F6767F6767F6767C67000000023A33B37CF7C7CF7C4CF4C4CC4C00F0
S32500000680000135337387F8787F8784F8484C8400000331F3131F3175F7575F7545F4545CDD
S325000006A045000375F7575F7575F7575F7575F7575C75000000021A11A15A55A54A448400F6
S325000006C0000323F2323F23AFFAFAFFAF8CF8C8CC8C00000311F1111F1151F5151F5141F42D
S325000006E0141C41000351F5151F5151F5151F5151F5151C510000000332F3232F327AF7A75E
S32500000700AF7A48F4848C4800000115117185F8585F8584F8484C8400000333F3333F3373F0
With wireshark I observed what is sent:
First packet (only printable characters, I masked some values due to privacy):
`5]_E;@7PVP1POST / HTTP/1.1
Accept-Encoding: gzip,deflate
Connection: keep-alive
Authorization: Digest username="XXXXX", realm="YYYYY", nonce="54", uri="/", response="470a39d6cf0af17889acddbd26d80a9c", qop=auth, nc=00000009, cnonce="29de2b99d6d92986"
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Host: 192.168.1.20
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Keep-Alive: 300
Content-Length: 3362138
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Content-Type: multipart/form-data; boundary=---------------------------826062028116
Referer: http://192.168.1.20/?filesystem=1
Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
Second packet(only printable characters - first line chars are some header values of the packet):
`5]_E;@5PXP)
S32500000500545F4545F4545F4545F4545C45000000023A33B374F7474F7444F4444C4401E5F5
S32500000520EE7ECBFCBCBCCB0000013533537577574544440000021A11B154F5454F5444F42C
S32500000540444C44000354F5454F5454F5454F5454F5454C54000000021A11B154F5454F541F
S3250000056044F4444C4400000323F2323F23A6FA6A6FA684F8484C8400000311F1111F11556F
S32500000580F5555F5545F4545C45000355F5555F5555F5555F5555F5555C55000000012522E8
S325000005A05265665645444400000331F3131F31F8FF8F8FF8C8FC8C8CC8000001151151152D
S325000005C0115115114100011511511511511511410000000312F1212F1252F5252E524A4414
S325000005E08400021A11B121F2121F21ACFACACFAC8CBBBBBBBBBBBBBBBBB5227211F1111F1A
S325000006001153F5353F5343F4343D4325225225227253F5353F5353F5353F5353F5353C534D
S325000006200000000332F3232F3276F7676F7644F4444C440000013533738EF8E8EF8E8CF8F8
S32500000640C8CC8C0125225225227221F2121F2167F6767F6747F4747D4725225225227267D7
S32500000660F6767F6767F6767F6767F6767C67000000023A33B37CF7C7CF7C4CF4C4CC4C00F0
S32500000680000135337387F8787F8784F8484C8400000331F3131F3175F7575F7545F4545CDD
S325000006A045000375F7575F7575F7575F7575F7575C75000000021A11A15A55A54A448400F6
S325000006C0000323F2323F23AFFAFAFFAF8CF8C8CC8C00000311F1111F1151F5151F5141F42D
S325000006E0141C41000351F5151F5151F5151F5151F5151C510000000332F3232F327AF7A75E
S32500000700AF7A48F4848C4800000115117185F8585F8584F8484C8400000333F3333F3373F0
S32500000720F7373F7341F4141C41000373F7373F7373F7373F7373F7373C730000000332F30C
S32500000740232F32
Reproducible: Always
Steps to Reproduce:
1. Use a formular for file-uploading on any server in the LAN
2. Upload a file bigger than several MBs
3. Observe by Wireshark what is sent
Actual Results:
First packet of [TCP segment if a reassembled PDU] is correct
Second packet conains some part of the file sent, but not the beginning
Expected Results:
First packet with header
Second packet with rest of the header and beginning of the file data
Third packet containing following file data
With any other browsers the file-upload works properly on same PCs and formular...
Updated•17 years ago
|
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
Version: unspecified → 1.9.0 Branch
Comment 1•17 years ago
|
||
This works fine for me with FF3.02 and Seamonkey trunk for example here in bugzilla.
| Reporter | ||
Comment 2•17 years ago
|
||
I tested it on the egroupware and mediawiki upload site on our internal server, too... File size 2.7 MB, text. Same behaviour: FF 3.0.2 fails, other browser work...
Interesting part is, that the beginning of the file is displayed in the Firefox incl. the missing header part. But the data displayed was never sent by any device in the network (according to Wireshark). And the displayed data is never sent to network...
Comment 3•17 years ago
|
||
You have Bitdefender on your computer, right? If yes, this is dup of bug #463579.
| Reporter | ||
Comment 4•17 years ago
|
||
You're right... That's the problem... BD stays deinstalled from now on.
| Reporter | ||
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•