Re: nsIChannel.contentChannel

2005-09-13 Thread Boris Zbarsky
Michael Vincent van Rantwijk wrote: Yikes, I assumed to be using some random fake domain name There are standard "fake" domain names to use, as documented in the DNS RFCs (eg example.com) if you need a "fake" domain name. -Boris ___ Mozilla-netlib

Re: nsIChannel.contentChannel

2005-09-13 Thread Michael Vincent van Rantwijk
Christian Biesinger wrote: Michael Vincent van Rantwijk wrote: (I didn't reply to the original message because the from address looks forged) You mean my e-mail address? Yes, indeed. Please note that I use <[EMAIL PROTECTED]> in order to prevent spam, but if I should change it...just say s

Re: nsIChannel.contentChannel

2005-09-13 Thread Boris Zbarsky
Michael Vincent van Rantwijk wrote: I don't think that there's anything guaranteed to work in this huge and constantly changing code base, but at least it works right now. The things that are guaranteed to work are documented as such with frozen interfaces or frozen contracts. -Boris ___

Re: nsIChannel.contentChannel

2005-09-13 Thread Christian Biesinger
Michael Vincent van Rantwijk wrote: (I didn't reply to the original message because the from address looks forged) You mean my e-mail address? Yes, indeed. Please note that I use <[EMAIL PROTECTED]> in order to prevent spam, but if I should change it...just say so and I will ;) I'm not a

Re: nsIChannel.contentChannel

2005-09-13 Thread Michael Vincent van Rantwijk
Boris Zbarsky wrote: Michael Vincent van Rantwijk wrote: It's "available" at any time. If you're asking at what point it could depend on what the server returned, that's after OnStartRequest or after open() returns. I hoped that, but that's not the case because it throws JS errors on the JS

Re: nsIChannel.contentChannel

2005-09-13 Thread Boris Zbarsky
Michael Vincent van Rantwijk wrote: It's "available" at any time. If you're asking at what point it could depend on what the server returned, that's after OnStartRequest or after open() returns. I hoped that, but that's not the case because it throws JS errors on the JS console if you try to

Re: nsIChannel.contentChannel

2005-09-13 Thread Michael Vincent van Rantwijk
Christian Biesinger wrote: Boris Zbarsky wrote: [nsIChannel.contentType is] "available" at any time. http://lxr.mozilla.org/seamonkey/source/netwerk/protocol/http/src/nsHttpChannel.cpp#3198 doesn't look like it is I filed https://bugzilla.mozilla.org/show_bug.cgi?id=307870 to improve

Re: nsIChannel.contentChannel

2005-09-13 Thread Christian Biesinger
Boris Zbarsky wrote: [nsIChannel.contentType is] "available" at any time. http://lxr.mozilla.org/seamonkey/source/netwerk/protocol/http/src/nsHttpChannel.cpp#3198 doesn't look like it is I filed https://bugzilla.mozilla.org/show_bug.cgi?id=307870 to improve the docs for this attribute

Re: nsIChannel.contentChannel

2005-09-13 Thread Michael Vincent van Rantwijk
Boris Zbarsky wrote: Michael Vincent van Rantwijk wrote: Lets assume that the correct content type is specified/send by the server, so when exactly will http://lxr.mozilla.org/seamonkey/source/netwerk/base/public/nsIChannel.idl#140 be available? It's "available" at any time. If you're ask

Re: nsIChannel.contentChannel

2005-09-11 Thread Boris Zbarsky
Michael Vincent van Rantwijk wrote: Lets assume that the correct content type is specified/send by the server, so when exactly will http://lxr.mozilla.org/seamonkey/source/netwerk/base/public/nsIChannel.idl#140 be available? It's "available" at any time. If you're asking at what point it c