starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 08:45:58 +03:00

[GH-ISSUE #16] GET on my Glitch API doesn't work #6

New issue

Closed

opened 2026-03-16 12:41:43 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 12:41:43 +03:00

Owner

Originally created by @aashutoshrathi on GitHub (Aug 22, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/16

Describe the bug
A simple GET request on http://aashutoshrathi.glitch.me/api/self/gh gives the error

To Reproduce
Steps to reproduce the behavior:

Go to https://liyasthomas.github.io/postwoman/
Select Method as "GET"
URL as http://aashutoshrathi.glitch.me
And Path as /api/self/gh
Then send a request.

Expected behavior

It should result in response same as http://aashutoshrathi.glitch.me/api/self/gh

Screenshots

Originally created by @aashutoshrathi on GitHub (Aug 22, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/16 **Describe the bug** A simple GET request on http://aashutoshrathi.glitch.me/api/self/gh gives the error **To Reproduce** Steps to reproduce the behavior: 1. Go to https://liyasthomas.github.io/postwoman/ 2. Select Method as "GET" 3. URL as `http://aashutoshrathi.glitch.me` 4. And Path as `/api/self/gh` 5. Then send a request. **Expected behavior** It should result in response same as http://aashutoshrathi.glitch.me/api/self/gh **Screenshots** ![image](https://user-images.githubusercontent.com/21199234/63550738-ee71c600-c550-11e9-818b-d4a94c6da078.png)

kerem

2026-03-16 12:41:43 +03:00

closed this issue
added the
duplicate
label

kerem commented

2026-03-16 12:42:01 +03:00

Author

Owner

@striebwj commented on GitHub (Aug 22, 2019):

Use https:// instead of http://.

Here is a screenshot from when I ran it using https://:

Here is a comment about http not working right now: link to comment

@striebwj commented on GitHub (Aug 22, 2019): Use https:// instead of http://. Here is a screenshot from when I ran it using https://: ![Screen Shot 2019-08-22 at 5 51 22 PM](https://user-images.githubusercontent.com/14165147/63552392-877aef80-c505-11e9-8cbb-139cd32e75f9.png) Here is a comment about http not working right now: [link to comment](https://github.com/liyasthomas/postwoman/issues/2#issuecomment-523870224)

kerem commented

2026-03-16 12:42:06 +03:00

Author

Owner

@liyasthomas commented on GitHub (Aug 23, 2019):

Possible duplicate of #2.
CORS is a server side security policy feature which blocks API calls from any non-HTTPS requests.

@liyasthomas commented on GitHub (Aug 23, 2019): Possible duplicate of #2. CORS is a server side security policy feature which blocks API calls from any non-HTTPS requests.

kerem commented

2026-03-16 12:42:11 +03:00

Author

Owner

@aashutoshrathi commented on GitHub (Aug 24, 2019):

I think I should close it then.

@aashutoshrathi commented on GitHub (Aug 24, 2019): I think I should close it then.

kerem commented

2026-03-16 12:42:16 +03:00

Author

Owner

@jamesscottbrown commented on GitHub (Aug 28, 2019):

This is not a CORS issue, but rather a Mixed Content issue. An XMLHttpRequest or fetch() request is considered "active content"; "mixed active content" such as a XMLHttpRequest or fetch() to an http:// URL from an https:// URL has been blocked by default since Firefox 23 and is also blocked by Chrome.

In this case, both URLs provide the same CORS headers:

< access-control-allow-origin: *
< access-control-allow-headers: Origin, X-Requested-With, Content-Type, Accept

Also, CORS does not block cross-origin requests: the same-origin policy prevents them by default, and CORS headers can be used to opt-in to allowing them.

@jamesscottbrown commented on GitHub (Aug 28, 2019): This is not a [CORS](https://developer.mozilla.org/en-US/docs/Glossary/CORS) issue, but rather a [Mixed Content](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content) issue. An `XMLHttpRequest ` or `fetch()` request is considered "active content"; "mixed active content" such as a `XMLHttpRequest ` or `fetch()` to an `http://` URL from an `https://` URL has been blocked by default since Firefox 23 and is also blocked by Chrome. In this case, both URLs provide the same CORS headers: ``` < access-control-allow-origin: * < access-control-allow-headers: Origin, X-Requested-With, Content-Type, Accept ``` Also, CORS does not block cross-origin requests: the *same-origin policy* prevents them by default, and *CORS* headers can be used to opt-in to allowing them.

kerem referenced this issue

2026-03-17 00:04:09 +03:00

[PR #6] [MERGED] History is sorted from latest to oldest #2358

kerem referenced this issue

2026-03-17 00:59:20 +03:00

[PR #1512] [MERGED] [Feat:Teams] Code restructure [1] #3367