Closed Bug 830883 Opened 11 years ago Closed 7 years ago

(request) Need to offer a way to make private requests

Categories

(Add-on SDK Graveyard :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: evold, Unassigned)

References

(Depends on 1 open bug)

Details

See https://developer.mozilla.org/en-US/docs/Supporting_per-window_private_browsing#Forcing_a_channel_into_private_mode for more info on how to do this.

I'm guessing there should be a `private` option for the Request constructor.
Flags: needinfo?(rFobic)
Maybe, but I'm not sure about the relevance to be honest. My guess would be that private XHRs do not cache or store cookies. I don't thin we do later anyway.

Can we find out how behavior will be different before adding this option, for the very list documentation should be clear about how behavior changes if option is set
to `true`.
Flags: needinfo?(rFobic)
Josh can you answer Irakli'squestion in comment 1?  I don't know what all of the benefits of a private channel are either.
Flags: needinfo?(evold) → needinfo?(josh)
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: --- → 1.14
If a channel is private, it does not share cache entries with public channels, nor authentication cache entries, nor cookies. These things are all persisted and shared with other private channels in the same private session. It is important that this option be available for users.
Flags: needinfo?(josh)
Depends on: 841652
No longer blocks: sdk-pwpb-fx21
Whiteboard: [good first bug]
Is this still possible now after the change made in bug 820953 ?
Flags: needinfo?(rFobic)
Whiteboard: [good first bug]
(In reply to Erik Vold [:erikvold] [:ztatic] from comment #4)
> Is this still possible now after the change made in bug 820953 ?

You still can query XHR with a same nsIXMLHttpRequest interface and there for should be possible.
Flags: needinfo?(rFobic)
https://bugzilla.mozilla.org/show_bug.cgi?id=1399562
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.