Sep 28, 2021, 5:31:36 PM9/28/21
Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message as abuse
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Chromium Extensions, hrg...@gmail.com, salem...@gmail.com, Chromium Extensions, wOxxOm
This is crazy, I have stumbled upon bug 992700 literally years ago when I ran into the problem of having to access a REST API that can only be used with the "correct" origin header - and after long trial/error/research the blocking webRequest header-change was the only workaround that did the trick.
I was recently wondering if this workaround was still needed, turns out years later absolutely nothing was done about it.. no fix.. no improvement... yeah its just uhm.. affecting basic forms of web communication?!
Of course this has now become one of the countless show stoppers/problems while trying to migrate to MV3 as it has for a lot of other people around here...
What about declarativeNetRequest? When I looked into it last year it didn't have all the header changing capabilities yet etc.
But I already have an eerie gut feeling that there is some horrible exception looming like a dark cloud.. that for some bizarre reason origin (and prob referer/referrer as well) headers can't be changed via that API? (at least not to what would make sense, lol)
Or has anybody here succeeded in doing so?
At this point it feels like some kind of survival reality show.. find the horrible hacky workaround of the week to make some basics work in MV3...