starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #175] Allow HTTP (not HTTPS) on postwoman.io #68

New issue

Closed

opened 2026-03-16 13:09:11 +03:00 by kerem · 20 comments

kerem commented

2026-03-16 13:09:11 +03:00

Owner

Originally created by @NBTX on GitHub (Oct 1, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/175

Originally assigned to: @hosseinnedaee on GitHub.

Currently postwoman.io redirects insecure requests to HTTPS.
Whilst this is often desirable, it prevents us from testing HTTP-only sites.

So essentially, we just need to disable this redirect.

Originally created by @NBTX on GitHub (Oct 1, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/175 Originally assigned to: @hosseinnedaee on GitHub. Currently postwoman.io redirects insecure requests to HTTPS. Whilst this is often desirable, it prevents us from testing HTTP-only sites. So essentially, we just need to disable this redirect.

kerem

2026-03-16 13:09:11 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 13:09:27 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 2, 2019):

Browser will block any resources (scripts , link , iframe , XMLHttpRequest, fetch) to download if original html page is in https and requested resources are in http.

Browser throws an Mixed Content error.

https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content

Only work around I found is to tweak browser security policies and allow http requests.

I'll update when I find another tweak.

@liyasthomas commented on GitHub (Oct 2, 2019): Browser will block any resources (scripts , link , iframe , XMLHttpRequest, fetch) to download if original html page is in https and requested resources are in http. Browser throws an Mixed Content error. > https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content Only work around I found is to tweak browser security policies and allow http requests. ![Screen Shot 2019-10-02 at 9 29 35 AM](https://user-images.githubusercontent.com/10395817/66017174-51169400-e4f7-11e9-931c-f0c4abeaae29.png) I'll update when I find another tweak.

kerem commented

2026-03-16 13:09:32 +03:00

Author

Owner

@hosseinnedaee commented on GitHub (Oct 11, 2019):

Maybe we should use a proxy server. send the request to proxy server fetch HTTP request on the server and then return back the response to Postwoman client.

@hosseinnedaee commented on GitHub (Oct 11, 2019): Maybe we should use a proxy server. send the request to proxy server fetch HTTP request on the server and then return back the response to Postwoman client.

kerem commented

2026-03-16 13:09:37 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 11, 2019):

Proxy implementation with Nuxt middleware is planned. @hosseinnedaee would you like to work on this feature?

@liyasthomas commented on GitHub (Oct 11, 2019): Proxy implementation with Nuxt middleware is planned. @hosseinnedaee would you like to work on this feature?

kerem commented

2026-03-16 13:09:42 +03:00

Author

Owner

@hosseinnedaee commented on GitHub (Oct 11, 2019):

@liyasthomas yeah sure
do you have any idea about implementation or I just start to work on it?

@hosseinnedaee commented on GitHub (Oct 11, 2019): @liyasthomas yeah sure do you have any idea about implementation or I just start to work on it?

kerem commented

2026-03-16 13:09:48 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 11, 2019):

@hosseinnedaee #2 had an active discussion around implementing middleware for proxy. This not only allow us to request for http but also solves CORS issues. NBTX is busy and couldn't follow this.

Later our team took it to telegram group chat for further discussions. Follow from this thread for discussion https://t.me/postwoman_app/72

https://blog.lichter.io/posts/nuxt-with-an-api/ this article discusses different methods for implementing middleware.

@liyasthomas commented on GitHub (Oct 11, 2019): @hosseinnedaee #2 had an active discussion around implementing middleware for proxy. This not only allow us to request for http but also solves CORS issues. NBTX is busy and couldn't follow this. Later our team took it to telegram group chat for further discussions. Follow from this thread for discussion https://t.me/postwoman_app/72 https://blog.lichter.io/posts/nuxt-with-an-api/ this article discusses different methods for implementing middleware.

kerem commented

2026-03-16 13:09:53 +03:00

Author

Owner

@hosseinnedaee commented on GitHub (Oct 12, 2019):

@liyasthomas Assign me to this issue.

@hosseinnedaee commented on GitHub (Oct 12, 2019): @liyasthomas Assign me to this issue.

kerem commented

2026-03-16 13:09:58 +03:00

Author

Owner

@frankli0324 commented on GitHub (Nov 19, 2019):

websocket support on this?

@frankli0324 commented on GitHub (Nov 19, 2019): websocket support on this?

kerem commented

2026-03-16 13:10:03 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 19, 2019):

@NBTX is working on proxy mode for WebSocket.

@liyasthomas commented on GitHub (Nov 19, 2019): @NBTX is working on proxy mode for WebSocket.

kerem commented

2026-03-16 13:10:08 +03:00

Author

Owner

@frankli0324 commented on GitHub (Apr 17, 2020):

need help？

@frankli0324 commented on GitHub (Apr 17, 2020): need help？

kerem commented

2026-03-16 13:10:13 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 17, 2020):

@frankli0324 we would love to have this feature implemented. do contribute.

@liyasthomas commented on GitHub (Apr 17, 2020): @frankli0324 we would love to have this feature implemented. do contribute.

kerem commented

2026-03-16 13:10:18 +03:00

Author

Owner

@frankli0324 commented on GitHub (Apr 18, 2020):

will take a look next week... got some schedules this weekend

@frankli0324 commented on GitHub (Apr 18, 2020): will take a look next week... got some schedules this weekend

kerem commented

2026-03-16 13:10:23 +03:00

Author

Owner

@frankli0324 commented on GitHub (Apr 28, 2020):

what I've done so far:

I tried to create a single nginx server configuration for anyone who wants to build up their own proxy server installing as less things as possible:

server {
	server_name your_own_doman;
	listen 443 ssl;
	include /etc/nginx/conf.d/ssl; # certificate, key
	resolver 8.8.8.8;
	location / {
		if ( $arg_target = '' ) { return 403 'null target'; }
		if ( $arg_scheme = '' ) { set $arg_scheme 'http'; }
		if ( $arg_scheme = 'ws' ) { set $arg_scheme 'http'; }
		if ( $arg_scheme = 'wss' ) { set $arg_scheme 'https'; }
		if ( $arg_scheme = 'http' ) { set $port '80'; }
		if ( $arg_scheme = 'https' ) { set $port '443'; }
		if ( $arg_port != '' ) { set $port $arg_port; }
		set $query '';
		set $path '';
		rewrite_by_lua_block { # on debian/ubuntu: libnginx-mod-http-lua
        	ngx.var.query = ngx.unescape_uri(ngx.var.arg_query)
			ngx.var.path = ngx.unescape_uri(ngx.var.arg_path)
        }
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "upgrade";
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_pass $arg_scheme://$arg_target:$port$path?$query;
	}
}

and made a little change

diff --git a/components/realtime/websocket.vue b/components/realtime/websocket.vue
index fba150e..9c7e56c 100644
--- a/components/realtime/websocket.vue
+++ b/components/realtime/websocket.vue
@@ -103,7 +101,19 @@ export default {
         },
       ]
       try {
-        this.socket = new WebSocket(this.url)
+        if (this.$store.state.postwoman.settings.PROXY_ENABLED) {
+          const original = new URL(this.url);
+          const proxy = new URL("your_proxy_server");
+          let proto = original.protocol;
+          proxy.searchParams.append("scheme", proto.substr(0, proto.length-1));
+          proxy.searchParams.append("target", original.hostname);
+          proxy.searchParams.append("port", original.port);
+          proxy.searchParams.append("path", original.pathname);
+          proxy.searchParams.append("query", original.searchParams.toString());
+          this.socket = new WebSocket(proxy);
+        }
+        else
+          this.socket = new WebSocket(this.url)
         this.socket.onopen = event => {
           this.connectionState = true
           this.communication.log = [

still trying to adopt the original version of http proxy server so we could use a single proxy for both types of requests

@frankli0324 commented on GitHub (Apr 28, 2020): what I've done so far: I tried to create a single nginx server configuration for anyone who wants to build up their own proxy server installing as less things as possible: ```conf server { server_name your_own_doman; listen 443 ssl; include /etc/nginx/conf.d/ssl; # certificate, key resolver 8.8.8.8; location / { if ( $arg_target = '' ) { return 403 'null target'; } if ( $arg_scheme = '' ) { set $arg_scheme 'http'; } if ( $arg_scheme = 'ws' ) { set $arg_scheme 'http'; } if ( $arg_scheme = 'wss' ) { set $arg_scheme 'https'; } if ( $arg_scheme = 'http' ) { set $port '80'; } if ( $arg_scheme = 'https' ) { set $port '443'; } if ( $arg_port != '' ) { set $port $arg_port; } set $query ''; set $path ''; rewrite_by_lua_block { # on debian/ubuntu: libnginx-mod-http-lua ngx.var.query = ngx.unescape_uri(ngx.var.arg_query) ngx.var.path = ngx.unescape_uri(ngx.var.arg_path) } proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass $arg_scheme://$arg_target:$port$path?$query; } } ``` and made a little change ```diff diff --git a/components/realtime/websocket.vue b/components/realtime/websocket.vue index fba150e..9c7e56c 100644 --- a/components/realtime/websocket.vue +++ b/components/realtime/websocket.vue @@ -103,7 +101,19 @@ export default { }, ] try { - this.socket = new WebSocket(this.url) + if (this.$store.state.postwoman.settings.PROXY_ENABLED) { + const original = new URL(this.url); + const proxy = new URL("your_proxy_server"); + let proto = original.protocol; + proxy.searchParams.append("scheme", proto.substr(0, proto.length-1)); + proxy.searchParams.append("target", original.hostname); + proxy.searchParams.append("port", original.port); + proxy.searchParams.append("path", original.pathname); + proxy.searchParams.append("query", original.searchParams.toString()); + this.socket = new WebSocket(proxy); + } + else + this.socket = new WebSocket(this.url) this.socket.onopen = event => { this.connectionState = true this.communication.log = [ ``` still trying to adopt the original version of http proxy server so we could use a single proxy for both types of requests

kerem commented

2026-03-16 13:10:28 +03:00

Author

Owner

@frankli0324 commented on GitHub (Apr 28, 2020):

demo: https://proxy.frankli.site
btw the original proxy is down

@frankli0324 commented on GitHub (Apr 28, 2020): demo: https://proxy.frankli.site btw the original proxy is down

kerem commented

2026-03-16 13:10:33 +03:00

Author

Owner

@fzyzcjy commented on GitHub (Jul 8, 2020):

Any progress? When developing it is very common to deploy on localhost with HTTP not HTTPS. Thus this feature is very desired and will be commonly used.

Thanks!

p.s. @franeli0324's site seems to be down.

@fzyzcjy commented on GitHub (Jul 8, 2020): Any progress? When developing it is very common to deploy on `localhost` with HTTP not HTTPS. Thus this feature is very desired and will be commonly used. Thanks! p.s. @franeli0324's site seems to be down.

kerem commented

2026-03-16 13:10:38 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jul 8, 2020):

For localhost endpoints, you should install Browser Extension (link in readme). For other non-https endpoints turn-on Proxy from Settings> Proxy.

*The latest Chrome extension is having a minor bug which has been fixed but is currently under review. Kindly use another browser (Firefox) local endpoints.

@liyasthomas commented on GitHub (Jul 8, 2020): For localhost endpoints, you should install Browser Extension (link in readme). For other non-https endpoints turn-on Proxy from Settings> Proxy. *The latest Chrome extension is having a minor bug which has been fixed but is currently under review. Kindly use another browser (Firefox) local endpoints.

kerem commented

2026-03-16 13:10:44 +03:00

Author

Owner

@fzyzcjy commented on GitHub (Jul 8, 2020):

Thanks! I just searched the plugin but find it 404, so I will turn to firefox or wait

@fzyzcjy commented on GitHub (Jul 8, 2020): Thanks! I just searched the plugin but find it 404, so I will turn to firefox or wait

kerem commented

2026-03-16 13:10:49 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jul 8, 2020):

Buggy version has been taken down - use Firefox / Proxy mode.

@liyasthomas commented on GitHub (Jul 8, 2020): Buggy version has been taken down - use Firefox / Proxy mode.

kerem commented

2026-03-16 13:10:54 +03:00

Author

Owner

@fzyzcjy commented on GitHub (Jul 8, 2020):

OK thanks!

By the way I find another solution: Disable Chrome's security check for this particular webpage in chrome's setting.

@fzyzcjy commented on GitHub (Jul 8, 2020): OK thanks! By the way I find another solution: Disable Chrome's security check for this particular webpage in chrome's setting.

kerem commented

2026-03-16 13:10:59 +03:00

Author

Owner

@idling-mind commented on GitHub (Aug 3, 2021):

I'm trying to access an internal http host. Couldnt get it working in anyway. Any suggestions?

@idling-mind commented on GitHub (Aug 3, 2021): I'm trying to access an internal http host. Couldnt get it working in anyway. Any suggestions?

kerem commented

2026-03-16 13:11:04 +03:00

Author

Owner

@liyasthomas commented on GitHub (Aug 3, 2021):

@idling-mind turn on Proxy Mode from Settings.

@liyasthomas commented on GitHub (Aug 3, 2021): @idling-mind turn on Proxy Mode from [Settings](https://hoppscotch.io/settings).

kerem referenced this issue

2026-03-17 00:06:03 +03:00

[PR #68] [MERGED] Request headers #2391