Closed
Bug 215769
Opened 22 years ago
Closed 21 years ago
shop.paycash.ru - Alert: The connection has terminated enexpectedly
Categories
(Tech Evangelism Graveyard :: Other, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: relf, Unassigned)
References
()
Details
Linux build 2003080105
On attempt to connect provided URL, Mozilla alerts:
"The connection to shop.paycach.ru has terminated unexpectedly. Some data may
have been transferred."
Linux Konqueror browser opens the URL without any problems.
The URL is referred from
http://www.monetaexpress.com/index.php?lang=en&page=transfer
Comment 1•22 years ago
|
||
WFM 2003081004 PC/WinXP
![]() |
||
Comment 2•22 years ago
|
||
Worksforme also with Linux trunk build 2003-08-09-05. What HTTP settings are
you using (protocol version, whether pipelining is on, etc).
Comment 3•22 years ago
|
||
WFM, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030810
Mozilla Firebird/0.6.1+.
Comment 4•22 years ago
|
||
WFM using 2003080304 WinXP, HTTP1.1 + Pipelining, no proxy.
Comment 5•22 years ago
|
||
wfm with win2k build 20030810..
Comment 6•22 years ago
|
||
WFM too, but after reloading the page a few times I got:
Internal Server Error 500
Exception: EOutOfMemory
Message: Out of memory
Comment 7•22 years ago
|
||
Reporter, does the problem still occur with Mozilla 1.5b?
Comment 8•22 years ago
|
||
Reporter does not respond and I count WFM from 6 different people here.
It could have been a temporary server problem...
-> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 9•22 years ago
|
||
Sorry for delay.
I still see the bug with Linux build 2003091605.
Reopenning...
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
![]() |
||
Comment 10•22 years ago
|
||
That's nice. Please see comment 2 and actually provide some useful information?
Reporter | ||
Comment 11•22 years ago
|
||
I use HTTP 1.1 with Keep-alive and Pipelining are On.
No proxy.
What else might be interesting?
Reporter | ||
Comment 12•22 years ago
|
||
I've just changed HTTP to 1.0 and turned off Keep-alive and Pipelining.
Still see the bug.
Reporter | ||
Comment 13•22 years ago
|
||
Well... I've found a reason for the bug. One need to disable all 56-bit and
lower SSL encryption support to see the described alert.
![]() |
||
Comment 14•22 years ago
|
||
In other words the server is broken and just terminates the connection instead
of properly returning an error to the SSL connection attempts?
Over to PSM to see whether we could report a better error here, but it's sort of
doubtful...
Assignee: darin → ssaux
Status: UNCONFIRMED → NEW
Component: Networking: HTTP → Client Library
Ever confirmed: true
Product: Browser → PSM
QA Contact: httpqa → bmartin
Version: Trunk → 2.4
Comment 15•21 years ago
|
||
The reported error code was added to PSM recently (that is, it is one of
the most recent additions to PSM) to detect and report a specific problem.
As I recall, the explanation is as follows. This is from memory, and
it's late, so this may not be 100%.
mozilla connects to the server, does the SSL handshake, and sends the request
which may include post data, etc.
Server drops the connection without any reponse.
mozilla would retry this, repeating this loop up to some number of times.
Trouble is, each time it sent the request, the request might be making a
purchase or doing some other transaction. So, the idea was to stop the
retry loop when data had actually been sent, notifying the user that the
user's request had been sent and a transaction may have been completed.
Sounds like a bad server to me.
![]() |
||
Comment 16•21 years ago
|
||
OK. Evang.
Assignee: ssaux → other
Component: Client Library → Other
Product: PSM → Tech Evangelism
QA Contact: bmartin → other
Version: 2.4 → unspecified
Reporter | ||
Comment 17•21 years ago
|
||
The bug is gone.
Status: NEW → RESOLVED
Closed: 22 years ago → 21 years ago
Resolution: --- → WORKSFORME
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•