If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

socket transport not handling non-http servers in http:// urls

VERIFIED FIXED in M10

Status

()

Core
Networking
P3
normal
VERIFIED FIXED
18 years ago
8 months ago

People

(Reporter: Judson Valeski, Assigned: rpotts (gone))

Tracking

Trunk
All
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

18 years ago
I'm using apprunner. The url is correct. It's an extreme case to illustrate the
problem which is actually fairly common.

When a host exists (is resolvable) but isn't running an http server (or it's
server is down), we crash in
nsresult nsHTTPChannel::ResponseCompleted(nsIChannel* aTransport)
{
    return m_pHandler->ReleaseTransport(aTransport);
}

the raw pointer in m_pHandler is bad.

We need to somehow "fail" when we run into a server that is resolvable, but not
connectable on port 80.

In the old world we would time out and eventually timeout with a "host not
responding" msg.

Updated

18 years ago
Target Milestone: M9
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: M9 → M10
(Assignee)

Comment 1

18 years ago
This bug has been fixed on the M9 branch.

I'll close it out when I merge the changes back onto the tip.
-- rick
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

18 years ago
I've landed the M9 branch...

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 3

18 years ago
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
You need to log in before you can comment on or make changes to this bug.