Something like “decentraleyes†for Privoxy…
|
Apr. 04, 2019, 02:16 AM
(This post was last modified: Apr. 04, 2019 02:18 AM by JJoe.)
Post: #25
|
|||
|
|||
RE: Something like “decentraleyes†for Privoxy…
(Apr. 03, 2019 05:10 PM)vlad_s Wrote: I am not well versed in this. "This" is always changing. So, we are all always learning. I'm not sure Privoxy can do this and as I understand it... Your browser requests yastatic.net/jquery/2.1.4/jquery.min.js. Privoxy returns a redirect (302) to https://192.168.2.1/decentraleyes/jquery/2.1.4/jquery.min.js. Your browser requests https://192.168.2.1/decentraleyes/jquery/2.1.4/jquery.min.js. 192.168.2.1 returns (200) jquery.min.js. Privoxy's redirect response (302) AND 192.168.2.1 server's file response (200) must contain Code: Access-Control-Allow-Origin: * Can Access-Control-Allow-Origin header be added to Privoxy's redirect (302) response? BTW: The sidki set adds 'unsafe-inline' for the inline scripts that it adds to the page. The next set will not add 'unsafe-inline'. If you don't need 'unsafe-inline', don't add it. |
|||
« Next Oldest | Next Newest »
|