Closed
Bug 325327
Opened 19 years ago
Closed 19 years ago
sitecom router crashes after sending password
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 137155
mozilla1.9alpha1
People
(Reporter: tychobismeijer, Assigned: darin.moz)
Details
(Whiteboard: [DUPEME])
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; nl; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; nl; rv:1.8) Gecko/20051111 Firefox/1.5
When I try to login to my sitecom wireless router(11 Mbps - 4p Switch 10/100 Mbps - Printer Server) the router crashes. When I login with Internet Explorer it doesn't happen and I can administrate the router.
When examining send TCP packets the problem seems to be that firefox sends the pasword in a separate package. IE does send it directly in the first package.
The router immediatly crashes when it sees no password in the first package I think. (stupid unwanted security!)
Reproducible: Always
Steps to Reproduce:
1.Go to your sitecom admin pagefor example: http://192.168.123.254/
2.Fill in your password and click login
Actual Results:
Router crashes and needs a reset.
Expected Results:
Getting loged in the router
I included TCP packages sent by IE and by Mozilla Firefox.
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Reporter | ||
Comment 3•19 years ago
|
||
Assignee | ||
Comment 4•19 years ago
|
||
This is not the first report of problems caused by this behavior in FF. Though there is nothing we can do to prevent chunking in TCP, we can encourage the TCP stack to put everything in a single packet by adding some buffering to FF.
I think this may actually be a duplicate bug report.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Whiteboard: [DUPEME]
Target Milestone: --- → mozilla1.9alpha
Assignee | ||
Comment 5•19 years ago
|
||
*** This bug has been marked as a duplicate of 137155 ***
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•