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

Local proxy settings #4045

Closed
szyb opened this issue Jan 10, 2018 · 10 comments
Closed

Local proxy settings #4045

szyb opened this issue Jan 10, 2018 · 10 comments
Assignees
Projects

Comments

@szyb
Copy link

szyb commented Jan 10, 2018

This problem occurs in standalone windows version.
I have local proxy installed and all traffic goes through this proxy. Proxy is configured in Windows proxy settings. I'm trying to sent GET request to http localhost service. In Windows proxy settings I set "Do not use proxy for local connections" (which is most likely not taken into account)
Proxy settings in Postman are set to "Use system Proxy"

The error is: Could not get any response
Moreover when I use Postman for Chrome then everything works fine.

App Details:

Postman for Windows
Version 5.5.0
win32 10.0.16299 / x64

Issue Report:

  1. Did you encounter this recently, or has this bug always been there:
    Always
  2. Expected behaviour:
    Response from localhost service
  3. Console logs (http://blog.getpostman.com/2014/01/27/enabling-chrome-developer-tools-inside-postman/ for the Chrome App, View->Toggle Dev Tools for the Mac app):
    None for now
  4. Screenshots (if applicable)
@SamvelRaja
Copy link

Can you share us the screenshot of the postmanconsole?
view -> show postman console, this will give us much information to debug thing faster.

@szyb
Copy link
Author

szyb commented Jan 10, 2018

Sure, here you go. "Invalid protocol 127.0.0.1" it says...
postman

@harryi3t
Copy link

Possible duplicate of #3667

@harryi3t
Copy link

harryi3t commented Jan 10, 2018

@szyb

Since you have selected "Do no use proxy for local addresses", the request should not go through the proxy.

But there is an exception to this, if there is an environment variable is set up for proxy (http_proxy, https_proxy, HTTP_PROXY or HTTPS_PROXY) then Postman will use that.

Also, in that case, we expect the protocol to be present. This error is seen when you have an environment variable like

http_proxy=127.0.0.1

If this is the case, can you try changing it to

http_proxy=http://127.0.0.1

If not, please share a screenshot of your proxy configuration.

@szyb
Copy link
Author

szyb commented Jan 10, 2018

@harryi3t
Yes, I have http_proxy setup. Changing it to "http://127.0.0.1" haven't solved my problem due to my configuration (explained below). I just cannot use proxy to local connections - it just don't work in my case. When I remove this environment variable then it works fine. But I would like to have it defined.

My configuration is:
I have local proxy (port 4480) which don't requires authentication (available only from localhost). Local proxy uses Non-ICP cascading and it just connects to my corporate proxy server which requires NTLM authentication, however my local proxy is already setup with valid user name and password.
Now I just need to setup my windows proxy to use only local proxy server and I don't need to provide username/password in every application uses internet connection.

As you can see (if I explained it well) the http_proxy variable is the reason why postman doesn't work in my case (for local services). Is there any option to ignore this variable in postman?

@harryi3t
Copy link

This is a known issue/feature request (a setting to disable proxy for env vars also)
For now, there are 3 workarounds

  1. You can remove the http_proxy env variable. Other non-terminal apps should continue to work using the proxy from operating system.
  2. If the above is not possible, then you can also set another env var NO_PROXY to the URL(s) that you wish should not go through the proxy
  3. You can also create a .bat file which un-sets the http_proxy variable and opens Postman app
set HTTP_PROXY=
set http_proxy=
set HTTPS_PROXY=
set https_proxy=
start Postman.exe

@szyb
Copy link
Author

szyb commented Jan 11, 2018

@harryi3t
I will go with 3rd option.
Thank you for your support

@SamvelRaja SamvelRaja added platform/windows Windows specific issues and removed needs-investigation labels Jan 11, 2018
@harryi3t harryi3t added this to Suggestion in Proxy Jan 11, 2018
@harryi3t harryi3t moved this from Suggestion to TODO in Proxy Jan 11, 2018
@harryi3t harryi3t added Proxy and removed platform/windows Windows specific issues labels Jan 11, 2018
@marcelocesards
Copy link

marcelocesards commented Apr 26, 2018

3rd option works to me:

set HTTP_PROXY=
set http_proxy=
set HTTPS_PROXY=
set https_proxy=
P:\Users\myUser\AppData\Local\Postman\Update.exe --processStart "Postman.exe"

@harryi3t
Copy link

Duplicate of #3942

@harryi3t harryi3t marked this as a duplicate of #3942 Jun 29, 2018
@ronnac
Copy link

ronnac commented Jun 11, 2019

In my case, what helped was:
setx http_proxy ""
setx https_proxy ""

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Proxy
TODO
Development

No branches or pull requests

5 participants