swagger editor

[AlexJMcloud]

Failed to fetch.
Possible Reasons:

CORS
Network Failure
URL scheme must be "http" or "https" for CORS request.

Until now, your editor cannot correctly identify the error codes.
The headers are all spelled out.

Access-Control-Allow-Headers: *
Access-Control-Allow-Origin: *

swagger.yaml:

schemes:

• https
  basePath: /api

[AlexJMcloud]

From another site I am making a request via curl. And I get the server responses that should be.
When will your editor be able to read headlines normally?

[hkosova]

What's the full error message on the Console tab in the browser dev tools?

[mathis-m]

From another site I am making a request via curl. And I get the server responses that should be.
When will your editor be able to read headlines normally?

Network errors can not be read by Javascript this is a Browser security feature. See Originally posted by @mathis-m in #6938 (comment)

Second thing is that CORS is something that the client decides to enforce or not, browsers do other tools like postman or curl don't.

[char0n]

Hi @AlexJMcloud,

In order to help you, we'd need more information.

• When you mentioned Editor did you mean https://editor.swagger.io/?
• Are you using swagger-editor npm package and integrating in your application?
• What is the OAS definition source (if you can disclose it)?

[AlexJMcloud]

Thanks. But I already solved this issue back in July.

…

Hi @AlexJMcloud, In order to help you, we'd need more information. When you mentioned Editor did you mean https://editor.swagger.io/?Are you using swagger-editor npm package and integrating in your application?What is the OAS definition source (if you can disclose it)? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOSor Android. [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#7346 (comment)", "url": "#7346 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dogukankrtlz]

How did you solve the issue ?

[muhammadrivaldy]

@AlexJMcloud how to fix that?

[o-medizadeh-Ard]

hi

how to fix that?

[AlexJMcloud]

Re: [swagger-api/swagger-ui] swagger editor (#7346) Hello, omid. Send 12 мая 2022 г., 0:44:10: hi how to fix that? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***> Yes.

…

--  Alex                         ***@***.***

[tobiolusa]

I am currently facing similar issue, How can I resolve it.

[o-medizadeh-Ard]

I am currently facing similar issue, How can I resolve it.

hi.
plese use this :
app.UseCors(x => x.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader());
in startup file Configure method.
and use app.UseSwaggerAndUI(); after the app.UseRouting(); and app.UseEndpoints(); in this method.
i resolve it with this way.