Event grid client requests returned 502 ProviderError

[sam961124]

• Package Name: @azure/arm-eventgrid
• Package Version: 14.1.0
• Operating system:
• [x] nodejs
  • version: 18.18.0
• [x] browser
  • name/version: Edge/123.0.2420.81
• [x] typescript
  • version: 5.4.3

Describe the bug Sending system topics create/list request through EventGridManagementClient returned 502 Bad Gateway error with a response:

{
    "error": {
        "code": "ProviderError",
        "message": "Resource provider 'Microsoft.EventGrid' failed to return collection response for type 'systemTopics'."
    }
}

We have also tried to send request through axios and fetch with Authorization header appended. However, the result is the same. This issue only happened in certain resource group. The weird thing is that it worked fine through Postman with the exact same request.

Screenshots

Response header

[github-actions[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl.

[kazrael2119]

@sam961124 , could you try again now? I can use sdk to create a system topic

[github-actions[bot]]

Hi @sam961124. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[sam961124]

@kazrael2119, we still cannot create a system topic or list system topics under some of subscriptions. We have also tried reregistering the EventGrid provider but it didn't work. However, it worked fine if we send requests through Postman or PowerShell. It seems that this issue only happened on the browser.

[kazrael2119]

@kazrael2119, we still cannot create a system topic or list system topics under some of subscriptions. We have also tried reregistering the EventGrid provider but it didn't work. However, it worked fine if we send requests through Postman or PowerShell. It seems that this issue only happened on the browser.

@sam961124 could you share with me your code and the full log ?

[sam961124]

@kazrael2119 I think we found the root cause. If we set the Accept-Language in the headers to a single language, then the API works fine. Postman didn't set Accept-Language header, so it worked. Please help take a look from API side if there's some logics related to this header.

[jeremymeng]

If the issue is the same when using our SDK, axios, or fetch, then it is likely a service issue.

[github-actions[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl.