Why do you think Redirection is the cause? It doesn’t use SharedArrayBuffers, and certainly not anywhere that Google would be able to see.
It is used by React, which is used by Redirection and Gutenberg, and probably other things.
Redirection does not use it on the front end at all, and Google Search console will not be able to find it as part of Redirection. If you are seeing this on your site then it is from something else that Google can find.
React has an outstanding issue for this:
https://github.com/facebook/react/issues/20829
Thread Starter
lechon
(@lechon)
Hi @johnny5
We assumed that it was redirection because on our site the only plugin that uses SharedArrayBuffers is Redirection (found on the file redirection.js).
We are using classic editor not Gutenberg so we are a bit at a lost in trying to find the source.
After doing some reading on the subject my understanding is that this can be mitigated if we add to the site header the following:
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
And we though about implementing this using. htaccess rule like this:
# Cross-Origin-Embedder-Policy: require-corp
<IfModule mod_headers.c>
Header set Cross-Origin-Embedder-Policy: "require-corp"
</IfModule>
# Cross-Origin-Opener-Policy: same-origin
<IfModule mod_headers.c>
Header set Cross-Origin-Opener-Policy: "same-origin"
</IfModule>
Does implementing this affects in anyway the way Redirection works?
Best regards,
As mentioned above, Redirection does not use React on the front end. It is purely for the admin UI and Google does not search that. Nothing is used on the front end.
I cannot say if those headers affect Redirection.
Thread Starter
lechon
(@lechon)
Hi @johnny5
Thanks for the feedback and explanation.
