starred/hoppscotch

Fork 0

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

[GH-ISSUE #56] Cannot use localhost as base url #19

New issue

Closed

opened 2026-03-16 12:48:03 +03:00 by kerem · 10 comments

kerem commented

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

Owner

Originally created by @profran on GitHub (Aug 25, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/56

Describe the bug
Unable to use 'localhost' as base url.

To Reproduce
Steps to reproduce the behavior:

Go to https://liyasthomas.github.io/postwoman/
Click on URL field
Type in: http://localhost:3002 (any port will do, I just happen to have a Node.js server running on that port)
Send button is disabled

Expected behavior
I expect the Send button to be enabled

Desktop (please complete the following information):

OS: Arch Linux (64-bit)
Browser: Chromium
Version: 75.0.3770.142 (Official Build)

Additional context
I cloned the repo and I think the issue is related to pages/index.vue line 247 on urlNotValid's validation pattern, I changed the return statement to always be false, and the problem was solved.

Originally created by @profran on GitHub (Aug 25, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/56 **Describe the bug** Unable to use 'localhost' as base url. **To Reproduce** Steps to reproduce the behavior: 1. Go to https://liyasthomas.github.io/postwoman/ 2. Click on URL field 3. Type in: http://localhost:3002 (any port will do, I just happen to have a Node.js server running on that port) 4. Send button is disabled **Expected behavior** I expect the Send button to be enabled **Desktop (please complete the following information):** - OS: Arch Linux (64-bit) - Browser: Chromium - Version: 75.0.3770.142 (Official Build) **Additional context** I cloned the repo and I think the issue is related to pages/index.vue line 247 on urlNotValid's validation pattern, I changed the return statement to always be false, and the problem was solved.

kerem

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

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 12:48:19 +03:00

Author

Owner

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

This might be a possibile duplicate of #2
Its a restriction due to the CORS (Cross Origin Request Policy), there isn't a client side work around to this unless the host your trying to access should respond with the appropriate CORS headers.
Please refer to docs here: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
Quick solution is to use a HTTPS API host, which supports CORS

@liyasthomas commented on GitHub (Aug 25, 2019): This might be a possibile duplicate of #2 Its a restriction due to the CORS (Cross Origin Request Policy), there isn't a client side work around to this unless the host your trying to access should respond with the appropriate CORS headers. Please refer to docs here: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS Quick solution is to use a HTTPS API host, which supports CORS

kerem commented

2026-03-16 12:48:24 +03:00

Author

Owner

@profran commented on GitHub (Aug 25, 2019):

I first thought of that, but my Node.js API is configured to support CORS requests. I'm sure it's just the URL validation's pattern which expects an URL with a domain at the end (any_url + .com .co .ar .jp ...). I'll see if I can open a PR to solve the problem tomorrow.

@profran commented on GitHub (Aug 25, 2019): I first thought of that, but my Node.js API is configured to support CORS requests. I'm sure it's just the URL validation's pattern which expects an URL with a domain at the end (any_url + .com .co .ar .jp ...). I'll see if I can open a PR to solve the problem tomorrow.

kerem commented

2026-03-16 12:48:29 +03:00

Author

Owner

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

If that's the case, I'll surely look into it. You're welcomed to open a PR to fix it.

@liyasthomas commented on GitHub (Aug 25, 2019): If that's the case, I'll surely look into it. You're welcomed to open a PR to fix it.

kerem commented

2026-03-16 12:48:34 +03:00

Author

Owner

@NBTX commented on GitHub (Aug 25, 2019):

Ah yes, I know the issue, I had to mess with the regex to get websockets to work. I'll see if I can find some more permissive ones - and I'll add in IP addresses.

@NBTX commented on GitHub (Aug 25, 2019): Ah yes, I know the issue, I had to mess with the regex to get websockets to work. I'll see if I can find some more permissive ones - and I'll add in IP addresses.

kerem commented

2026-03-16 12:48:39 +03:00

Author

Owner

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

You could've opted to use two regex for URLValidation() 🤭

@liyasthomas commented on GitHub (Aug 25, 2019): You could've opted to use two regex for URLValidation() 🤭

kerem commented

2026-03-16 12:48:45 +03:00

Author

Owner

@NBTX commented on GitHub (Aug 25, 2019):

Yes, that was probably how I'd do it.

That said - is validation even necessary? Perhaps it would be ideal to just show an error if it fails to connect, like the websockets do, then to handle each edge case in regexes?

@NBTX commented on GitHub (Aug 25, 2019): Yes, that was probably how I'd do it. That said - is validation even necessary? Perhaps it would be ideal to just show an error if it fails to connect, like the websockets do, then to handle each edge case in regexes?

kerem commented

2026-03-16 12:48:50 +03:00

Author

Owner

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

Sooner or later, URL validation will be necessary. Anyway let's discuss.

@liyasthomas commented on GitHub (Aug 25, 2019): Sooner or later, URL validation will be necessary. Anyway let's discuss.

kerem commented

2026-03-16 12:48:55 +03:00

Author

Owner

@NBTX commented on GitHub (Aug 25, 2019):

Okay. I'll update the url validation to include the two regex checks in the mean time.

@NBTX commented on GitHub (Aug 25, 2019): Okay. I'll update the url validation to include the two regex checks in the mean time.

kerem commented

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

Author

Owner

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

@NBTX sendRequest() isn't firing. Can you check changes on URL validation

@liyasthomas commented on GitHub (Aug 25, 2019): @NBTX sendRequest() isn't firing. Can you check changes on URL validation

kerem commented

2026-03-16 12:49:05 +03:00

Author

Owner

@NBTX commented on GitHub (Aug 25, 2019):

Solved by #58

@NBTX commented on GitHub (Aug 25, 2019): Solved by #58

kerem referenced this issue

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

[PR #20] [MERGED] fix for pwa install issue #2367