blocked by CORS policy has ramped up

Question

blocked by CORS policy has ramped up

Closed this issue 3 years ago · 8 comments

Javier,
I'm not sure if Instagram is purposely causing trouble with acquiring remote instagram feeds but I've been watching the messages on my JS console and their changes to CORS policy have increased the number of JS "Instagram Feed: Request failed" errors dramatically.

On Monday everything was fine but on Wednesday I noted that several installations of jquery.instagramFeed were reporting a single fail and then rendering the feed. Today, I am able to render the feed but all 8 attempts are reporting failure in my JS console.

On a related note, I built and maintain the Drupal integration module for your JS library and there are currently some ~3000 installations so I am motivated to keep an eye on things.

Cheers,
Andrew

Answer 1 · 2021-03-12T18:30:10.000Z

It is Google. The problem is temporary. I have got it in one moment, but now everything is ok.

Answer 2 · 2021-03-12T18:43:37.000Z

It's Google? I'm not sure that I understand how that's occurring but I do see that now some feeds that were showing 8 errors and not resolving are now showing with a single error and one is now showing with no errors.

Is there anything we can do to mitigate the issue?

Thanks,
Andrew

Answer 3 · 2021-03-12T18:49:53.000Z

Is there anything we can do to mitigate the issue?

I am afraid not. The current solution (several tries, alternative google proxy and caching) is the best we have.

Answer 4 · 2021-03-12T18:56:46.000Z

are` now showing with a single error and one is now showing with no errors.

You can reduce the number of errors in the console by changing the host parameter.
#125 (comment)

Answer 5 · 2021-03-12T19:08:48.000Z

Thanks for pointing out the host parameter. I hadn't seen that earlier. I'll give that a shot and see how it responds.

Cheers,
Andrew

Answer 6 · 2021-03-12T21:24:25.000Z

@mahotilo, thanks for the tip about the host parameter. I believe that is the fix. I've updated my module to use it and it seems to have completely fixed it.

I'll close the issue.

Cheers,
Andrew

Answer 7 · 2021-03-12T21:31:24.000Z

The real workaround is proxying the request and use GraphQL (`user_id`` parameter)

Answer 8 · 2021-03-12T21:52:43.000Z

Awesome! I'll have to do some R&D locally on this but that might be something I add to the Drupal module. There are some really great features in your library. It makes adding and configuring a feed a breeze.

Thanks,
Andrew