DavidWells / DavidWells/analytics

Analytics behind a proxy

Open
#146 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.7k
Forks
267
PR merge metrics
No merged PRs in 30d

Description

Let me start by thanking you for this wonderful lib, I already use it in a couple of projects in our company.
Last week a new situation has a-raised, where we have an electron app, which needs to run behind a proxy.
Now the problem is, that the infra of the app is built in such a way that the requests go out from the main process of electron, so basically a nodeJs context (and not a browser) so proxy configs are not there by default.
For our REST Api, I needed to add an extra logic that resolves the proxy settings of the machine using the web Session of the chromium browser.

Bottom line, I need to do the same thing with the analytics module in order for the requests to go through the proxy (all other traffic will be blocked)

Is it somehow possible to tinker with the networking module of the lib? if so can you direct me in the right direction? If I'll end up having a good solution, I'll open a PR request with the changes for future needs of other devs:)

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no file or test; start by locating the analytics module's networking entry point and how Electron's main process can access the browser web Session proxy settings. Confirm the current request path, then define done as analytics requests working through the machine proxy in the Electron main process.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript, nodejs
Domain
desktop, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.