Darin Fisher wrote:
FWIW, maybe we should deprecate nsIChannel::owner, and change the JAR
channel to implement nsIJARChannel w/ a principal getter.
We could, if we moved the other owner consumers to property bag or something.
For what it's worth, I think that it should just be possible to get a
"principal" (or something QIing to one?) from channels in general... Then we
wouldn't need this thing where chrome channels use |owner| to mean their
intrinsic principals while javascript: and data: channels use it to mean the
principal they were opened with... and expect their callers to set it!
As in, for every channel it seems there are three principals around:
1) The principal to use for the checkLoadURI check or equiv.
2) The principal to use for the channel if nothing better is found (eg "caller
principal" for javascript:)
3) The final principal to use for a document loaded via that channel.
Not sure what the best setup is for dealing with these....
-Boris
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
