Tuesday, May 26, 2015

Production Incident 10: Default Proxy Or Proxy Or CORS When Remote Name Cannot be resolved

Issue: Remote Name cannot be resolved.

Scenario: When we call third party or cross domain api within our web api.

Resolution :
  1. Enable CORs at third party api Or
  2. Try to include default proxy
  3. Or specific proxy at your client web APi

<system.net>
    
    

  </system.net>
 
Or
<system.net>

http://proxy.XYZ
"usesystemdefault="True" />

</system.net>
 
Or
Enable Cors
 
Error Slab:

 
Post a Comment