Closed Bug 11318 Opened 25 years ago Closed 25 years ago

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

Categories

(Core :: Networking, defect, P3)

All
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: jud, Assigned: rpotts)

References

()

Details

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.
Target Milestone: M9
Status: NEW → ASSIGNED
Target Milestone: M9 → M10
This bug has been fixed on the M9 branch. I'll close it out when I merge the changes back onto the tip. -- rick
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I've landed the M9 branch...
Status: RESOLVED → VERIFIED
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.