Odds are, you are not impacted. We identified only a few dozen customers who had configured an open proxy, whether intentionally or by accident. All customers with an open proxy configured, and a custom domain, have already been contacted directly.
Thanks so much for reaching out. My apologies for the suboptimal experience here. Our team sent our communication with the above information to customers who were impacted via email, but it appears as though we did not send one to you. My apologies for the oversight-- I have shared this feedback with my team.
If you have any further questions at this time, I would be happy to answer them or loop in someone else who can.
@hillary Mostly I was wondering if the “communication” that was sent was merely a deprecation notice? Or did it have additional information as to suggested workaround(s) for the deprecation?
If it had suggested workarounds, I’d love to hear them if you could find and forward me that comm? Otherwise, at least I know about the deprecation now and will have to try and figure out something on my own.
Which is exactly why it was discontinued as it could have been easily abused by anyone to bypass CORS restrictions set by a server. It’s probably still possible, but we wanted to avoid letting anyone do it using our systems as it’s our systems that would take the impact.