Issues setting search service in production (CORS)

Question

From Scott Mitchell (@jazzlemonkey) via Twitter who tweets:

“Hi we are thinking of using the search service in production due to latency with our uk and Australian services but we are having major issues with CORS. We have tried setting the allow all option and explicitly creating rules for the incoming domains. It appears to be extremely intermittent sometimes sending the allow origin header in the response and sometimes not. We have tried reducing and then Increasing the "Max age in seconds" but we are still experiencing issues.....any ideas?? ”

Appreciate if you may be able to advise.

Tweet URL: Received over DM
 
Thanks,
@AzureSupport

Answer 1

Note: We also referred Scott to the content on http:/aka.ms/d1024658

Answer 2

Thanks Francis.

Note that the content you linked to is specific to Azure Storage, not Search. The CORS documentation on Search is on MSDN.

We'll need more details from the customer in order to troubleshoot this. Can you please tell them to e-mail me at [first name] dot [last name] at Microsoft with the following details:

• What browser(s) are you testing with? Does the issue occur for some browsers but not others?
• What is the name of your service and what region is it in?
• Can you give us an approximate time range of CORS requests that your application made (both failed and successful requests), so we can correlate with our logs?
• We need all the information that was blacked out in the screenshots.
• How are you passing the api-key to your service, and which api-key are you using (admin key or query key)?
• Does your scenario allow for publicly disclosing your query api-key (this is a requirement if you're calling Azure Search from the browser, since you need to pass your api-key on each request)?

Thanks,

-Bruce

Answer 3

This turned out to be a bug in Azure Search that only affected Basic SKU services. The fix has been deployed and we followed up with the customer offline.