Ingest-Client resets proxy settings

Open
#1,040 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
networking

Research direction

Start by tracing Ingest-Client initialization and identify where proxy settings are read or reset. Reproduce the behavior with an application configured with nonProxy exceptions, then verify that initialization preserves those settings and add a regression test if the existing test structure supports it.

Written by the indexing model from the issue text.

Description

An internal Application is set behind a proxy, with nonProxy exceptions.
Normally these work fine, but on initialisation of the Ingest-Client, the proxy settings are reset to the Systems environment.

We added an workaround by adding the nonProxy hosts by calling

System.setProperty("http.nonProxyHosts", "...");
System.setProperty("https.nonProxyHosts", "...");
Dominant language
Java
Stars
83
Forks
70
Avg merge
1d 7h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from snowflakedb/snowflake-ingest-java

All issues in snowflakedb/snowflake-ingest-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.