CORS errors showing in console for some requests to embeddable_blip and embeddable_identify

7 コメント

  • Robson Rosa de Almeida

    Hi, I'm facing this same problem.

    The header is not being set in some responses and it causes errors. For example, users are not being able to download files shared by our support team through the Web Widget Chat.

  • Anna Roussanova

    Hi folks, the widget team was rolling out a new backend change that caused some requests to be missing the Access-Control-Allow-Origin header. The requests in question were duplicates, so there was no impact to the functionality in the widget, but you did end up getting those CORS errors in the console. The underlying issue has since been fixed, so you shouldn't see any more errors now.

  • david sam

    I think its a common every one facing. I am experiencing issues with headers not being set in some responses, which causes errors. Regard :Scissor Hub

  • Eric Nelson
    Zendesk Developer Advocacy

    Hey David,

    Are you still experiencing this issue?

    Have a wonderful day!

    Eric Nelson | Manager - Developer Advocacy

  • Yanluis Ulloa

    Seems like this issue is happening again? Thanks for the support, this is messing our RUM monitoring. 

  • Cheeny Aban
    Zendesk Customer Care
    Hi Yanluis, 

    I suggest that you check if the troubleshooting steps from How can I troubleshoot CORS? will work on your issue. If none, you may initiate a conversation with us so we can further check. 
  • Caleb Pourchot

    Not sure if I should open up another ticket, but this is happening to us on the embeddable_search widget. Attached are the error in the console and the request headers from the OPTIONS request. There is no Access-Control-Allow-Origin header being sent.



Powered by Zendesk