Closed Bug 431580 Opened 17 years ago Closed 9 years ago

some network functions don't work

Categories

(Toolkit Graveyard :: XULRunner, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ksquirrel.iv, Unassigned)

Details

Attachments

(1 file)

2.14 KB, application/bzip2
Details
User-Agent: Opera/9.50 (X11; Linux i686; U; en) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008042904 Minefield/3.0pre It seemed that some network functions don't work. 1) Simple XMLHttpRequest example, plus simple TCP server written on Perl for testing (attach). If I run this server and them try to send a request to it from xul app, I get the following exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXMLHttpRequest.send]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://motest/content/motest.xul :: <TOP_LEVEL> :: line 30" data: no] 2) nsIServerSocket::asyncListen() fails. Comment XMLHttpRequest stuff in sample code and uncomment nsIServerSocket stuff. I got the following exception: [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIServerSocket.asyncListen]" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: chrome://motest/content/motest.xul :: <TOP_LEVEL> :: line 48" data: no] Both examples work fine in xulrunner-1.8. Reproducible: Always Steps to Reproduce: 1. Run attached xulapp with xulrunner-1.9 or firefox3 2. 3. Actual Results: Exceptions Expected Results: 1) Get response from Perl server in the first example 2) and begin to listen desired port in the second one
Attached file Testcase
Sample xul application with Perl server.
How to run Perl server: # ./server.pl 10000
it would be good to have just one issue per bug report...
Fixed... This thing MUST be documented, and I leave this bug unchanged until it will be well documented. For some reason mozilla-1.9 thinks that we are in offline mode by default, and it doesn't depend on "network.online" preference. This is not good. Using <browser> element and loadURI() is much more suprising. When trying to go online, it will show a message box "This document cannot be displayed while offline. To go online, uncheck Work Offline from the File menu." (yes, "File" menu in xulrunner). How to fix: // network doesn't work here... var ioService = Components.classes["@mozilla.org/network/io-service;1"]. getService(Components.interfaces.nsIIOService2); ioService.offline = false; // now network works...
XULRunner has been removed from the Mozilla tree: see https://groups.google.com/forum/#!topic/mozilla.dev.platform/_rFMunG2Bgw for context. I am closing all the bugs currently in the XULRunner bugzilla component, in preparation for moving this component to the graveyard. If this bug is still valid in a XULRunner-less world, it will need to be moved to a different bugzilla component to be reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: