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

Internet traffic not getting routed through configured proxy settings #136

Open
Galphat opened this issue Jul 7, 2023 · 3 comments
Open

Comments

@Galphat
Copy link

Galphat commented Jul 7, 2023

Proxy
Eclipse error
TestNg

This issue occurs in office network only.
After checking wth office support team they suggested to reach Eclipse support team since it was observed that internet traffic was not getting routed via configured proxy in Eclipse.
Eclipse version used:- 2021-12 (4.22.0)

@akurtakov
Copy link
Member

Two things:

  • Please report your OS as proxy support implementation differ between OSes
  • Please try latest Eclipse version (2023-06) as 2021-12 is no longer supported

@merks
Copy link
Contributor

merks commented Jul 7, 2023

It looks like windows. Shouldn’t the entries be check marked to be used?

@Bananeweizen
Copy link
Contributor

Bananeweizen commented Jul 9, 2023

Native on Windows means "use Internet settings as configured in system control". However, I have seen that not working quite often on company machines myself, therefore I always recommend to use "manual". It will look the same, but you then have to set the checkboxes and all the entries for user/password yourself. Also you may want to add *.yourcompany.com" to the exceptions.

If anyone wants to investigate why this doesn't work with native: My main assumptions are

  • "native" is interpreted as "don't use a proxy" somewhere in the code
  • the actual native settings are too complex to fully use them in the Java code somehow (e.g. our company has a proxy configuration driven by a *.pac file in system control, which is in fact Javascript that dynamically calculates the proxy address based on location and who knows what).

Bonus answer for anyone running into this at a later point of time: If your company uses an authenticating centralized proxy (with NTLM authentication based on your Windows account credentials), then please use a local configuration-less proxy like px to get rid of the authentication hazzle. px will authenticate on your behalf, using the active Windows session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants