[Bug - Partner Center] Entered URL is broken or invalid

[eliassorensen]

Describe the bug
I'm trying to update my extension (Velatir), but when saving, it fails on the Privacy Policy URL and Website URL fields with the error: "The entered URL(s) seem broken or invalid. Please verify that each URL is reachable.".

I have not changed anything on the DNS or website, so I'm unsure why this is not working. The URLs are perfectly valid and reachable.

[carlosjeurissen]

@eliassorensen since these checks happen client-side in the browser, this is probably a CORS issue. You can try adding the Access-Control-Allow-Origin header.

However, seems in general these checks should NOT happen on the client-side exactly because of potential CORS and webExtension interference issues.

[Rahul-Bauri]

@eliassorensen I have informed the engineering team regarding this issue, will let you know once I get back any update regarding this from their side, in the meantime could you please try to perform the workaround mentioned by @carlosjeurissen and see if it works.

[eliassorensen]

Hi Rahul,

I don't think it happens in the browser. I can see you make a request to https://partner.microsoft.com/en-us/dashboard/microsoftedge/api/UrlCheck?urlValue=https://www.velatir.com/privacy

And get this response: {"url":"https://www.velatir.com/privacy","status":429,"reachable":false,"redirected":false,"finalUrl":"https://www.velatir.com/privacy"}

I haven't changed anything, and it have always worked. I use Vercel for the hosting.

[carlosjeurissen]

@eliassorensen in that case they changed the behaviour. They used to do this check client-side. Thanks for verifying and checking! Still adding Access-Control-Allow-Origin could work.

[Rahul-Bauri]

Hi @eliassorensen This is the response I got from the Engineering team trying to resolve the error:

This is what we get when we try to fetch the url - 429 error, which is why it's failing. It seems to be an issue from your side. Please check.

[eliassorensen]

Hi again,

We are using Vercel and their WAF + Bot Protection. So something must have happened since they are now blocking your requests. We are using the out of the box configuration for Vercel, so I would expect that other Vercel customers might have issues as well.

Can you share the user agent you are using for the lookup? Then I'll see if I can create a rule to let it through!

[Rahul-Bauri]

@eliassorensen we just used bruno for snpshot above and in code we are just using normal http get call. Hope that helps!

[Rahul-Bauri]

Closing this issue, as its some issue with your side server, please open a new bug if you face any challenges in the future.

[eliassorensen]

@Rahul-Bauri I'm using Vercel - and using their default setup. So definitely something you need to sort out.