-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to send cookies in request (swagger-ui 3.x) #2895
Comments
At the moment, that configuration is not yet available in 3.x. If you require it, either use 2.x or consider submitting a PR to 3.x to add support for it. |
Just fired it up and having the same problem. But there is an option in the authorize modal to put in a cookie. Am I correct in assuming @HunDunDM had that option too, and it did not work? Or was that input field in the modal added since then, and it's supposed to work now? Confused. |
still not work now. I am waiting for this PR |
Not a robust solution
then work fine. |
+1 to add cookie management in Swagger 3... natively Crazy to have a spec, without proper implementation of it. Without any warning |
ui.fn.fetch.withCredentials = true This worked for me. Using Firefox 59.0.2 the CORS Everywhere extension |
I am slightly confused regarding what this is supposed to do? I am looking for a way for Swagger UI to load the Swagger JSON from a CORS location (the thing which is specified via If so, it doesn't work in neither Safari nor Chrome (on macOS). |
if set "enableCookies: true" in swagger-ui 2.x, it will send cookies in request.
But it don't work in 3.x.
What should I do?
The text was updated successfully, but these errors were encountered: