Could had directly used the cache of UserPreference store. But to also cover the case when getNextAvailablePort might adjust the port number if the cached port number is currently in use: Added proxyServerStatus to the global.rq namespace in Background process.

The proxy list is read and not overwritten based on it's value when Requestly is started. So any changes made while Requestly is running might be overwritten.

Fixes - https://github.com/requestly/requestly/issues/200

Initial commit is a revert of previously reviewed changes that were reverted here

Please review starting from the 2nd commit

The changes for settings default port are currently unreleased and require further changes to make them stable. In the mean time there are other important changes that need to be released first

Builds on top of #15 to use user preference default to restart the proxy when this value changes

Note: rewrites startProxyServer to typescript

Needs a follow up PR to

• remove passing ports from IPC call for launching apps
• Someway to handle running proxy sources (either restart the source with the new proxy port or for now just show some UI warning about expected failures when port changes)

Currently, we only have support for advanced filters in the browser extension. The desktop app doesn't support filters. All filters are not required immediately, we need an HTTP Method/Verb-based filter in the first cut.

Before windows 11, in order for system proxy settings to apply, we used a hacky approach to launch and kill a new internet explorer window. This is no longer required in windows 11, but with microsoft dropping support for Internet explorer from windows 11 onwards, this launches the following error dialog if we use exec

Using the Modify Response Rule, we are unable to access requestData it is always returning null

More context:

• the request is a POST request that has a body.
• the endpoint is an existing (real) endpoint
• using Modify Request Body Rule for the same request, we can access the requestData and change it successfully
• the issue is on the latest desktop app using chrome new profile

• Creates a utility called createError along with constants to denote cause for these custom errors
• Sends error.cause in both error object and metadata because chromium sanitises errors received via IPC - https://github.com/electron/electron/issues/24427

Hi, I'm new on the desktop app for Mac and I didn't find how to change the default port.

It starts on port 8080 and I'd like to change to something else, is this feature supported?

In case it is not supported, I would recommend to include this option, and usually port 8080 is really common for Java Spring applications, it would be useful for the default port to be something else (Fiddler uses 8888 as default).

Thank you.