User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170302120751 Steps to reproduce: Now the addon sdk listeners have httpChannel.loadFlags functionality Actual results: WebRequests don't have similar functionality Expected results: WebRequests must have load flags or similar functionality

can you give us the use case / priority of this for what you're trying to get done?

Use case. In Bug 1286681 a certificate with the sha1 hash was only used in the http redirect. Redirect was cached. To check the presence or absence of the certificates in this case, it is really only with the addition of capable of manage the cache flags of requests. Similarly, any redirection on the websites also sometimes need checks for their presence and it http headers.

fdsc: I don't understand the use case (what you wrote isn't actually a use case). You want to "check the presence or absence of the certificates", but why? You say these things need checks but not what kind of checks, for what reason, and what you would do in reaction to those checks. Are these things that Firefox should be doing and you're trying to fill in a hole? Are they specialized checks for a unique application?

It was just an example of the validation that is difficult without it. It is not necessary to dwell on the specific objectives of the inspection. The important thing is that without this feature, check out what cached very hard. Not necessarily that it was the certificates. It can be simple check where it is redirecting.

Hi fdsc, this has been added to the agenda for the June 13 WebExtension APIs triage meeting. Would you be able to join us? Wiki: https://wiki.mozilla.org/Add-ons/Contribute/Triage#Next_Meeting Agenda: https://docs.google.com/document/d/1A_M0YD86Plcs6eHyM2KXkDXY074BHZ3fZvaWXCljQLI/edit#

https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIWebNavigation#Load_Flags https://chrome.google.com/webstore/detail/super-cache/fglobbnbihckpkodmeefhagijjcjnbeh Maybe we have enough API? I can't confirm this with super-cache, it be break due to strange errors if modify files.

Bug 1322748 covers similar functionality, tentatively approved based on outcome of that.

Re-reading this with more time...it's probably not related to the security info in bug 1322748, I need to dig deeper.

(In reply to Shane Caraveo (:mixedpuppy) from comment #8) > Re-reading this with more time...it's probably not related to the security > info in bug 1322748, I need to dig deeper. Just like makeRequest({ nocache: true }), no relationship for scheme. I don't know whether we have similar functionality.

Re-reading this, I still do not understand the problem here. Are you needing to know if a request is cached? If so, you can find out using onBeforeRedirect. Or do you want to manage the cache flags to bypass cache if necessary?

Without actual clarity on what this request is about, I'm closing it.