Skip to content
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

'Try it out' API calls using HTTP, not HTTPS #63

Closed
JeremyCraigMartinez opened this issue Mar 7, 2019 · 6 comments
Closed

'Try it out' API calls using HTTP, not HTTPS #63

JeremyCraigMartinez opened this issue Mar 7, 2019 · 6 comments
Labels

Comments

@JeremyCraigMartinez
Copy link

The requests against the API for trying out an endpoint is not reading from schemes in the swagger.json. I'm getting a GET against an http:// even though my swagger definition is

{
  "swagger": "2.0",
  "info": {
    "version": "2019-03-04T21:51:15Z",
    "title": "API"
  },
  "host": "api.my-domain.com",
  "schemes": [
    "https"
  ],
...
@twskj
Copy link
Owner

twskj commented Mar 7, 2019

Thanks for reporting :)
I'll have a look in the evening.

@JeremyCraigMartinez
Copy link
Author

Awesome, thanks! I also noticed the same issue with the pet store docs

This is a Mixed Content call. Many browsers will block this by default.

@twskj
Copy link
Owner

twskj commented Mar 8, 2019

That generally means that when the document is served under https but trying to make an ajax call out to http endpoint usually get blocked by default. It's an expected behavior in Chrome and Firefox as far as I know

@twskj twskj added bug and removed investigate labels Mar 8, 2019
@twskj
Copy link
Owner

twskj commented Mar 8, 2019

It's a bug having only https should not show http option. I'll make some adjustment for this.

@twskj
Copy link
Owner

twskj commented Mar 23, 2019

I rolled out the fix in 0.2.3.
Now it should respect scheme from the input and show only what available.
Check it out

@twskj
Copy link
Owner

twskj commented Mar 29, 2019

I am closing this. If you still have problem, feel free to reopen.

@twskj twskj closed this as completed Mar 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants