Browser extension development question: is it still possible (including in Chrome!) to intercept response headers of all HTTP requests?
Don't need to modify them or anything, but I have an idea for an extension that identifies 'compatible' sites by a server-provided response header (to avoid having to inject any code into the page).
The header name is known upfront (and is a custom header), but it should be intercepted for every pageload that is visible to the user, regardless of domain.
@vincentb Hmm. Is that still available? Wasn't Chrome going to throw out that entire API?
@vincentb I think I'm thinking of regular webRequest; what with the (justified) panic around its deprecation preventing adblockers from continuing to work. But it seems that that's only webRequestBlocking? Which I don't think I need.
@joepie91 Yes it seems that way indeed. Not too familiar with the whole manifest V3 migration regarding adblockers. I think it it safe to say that listening for specific headers will not go away anytime soon.
@joepie91 Maybe you mean "declarativeWebRequest" https://developer.chrome.com/docs/extensions/reference/declarativeWebRequest/ ? That one is deprecated but I don't think they will deprecate webRequest