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

How do I add an exempt to proxying? #121

Open
working-name opened this issue Dec 20, 2024 · 2 comments
Open

How do I add an exempt to proxying? #121

working-name opened this issue Dec 20, 2024 · 2 comments
Labels
question Further information is requested

Comments

@working-name
Copy link

Summary

A site that has google's recaptcha will not be able to load it via requestly's proxy. It somehow detects it or whatever is going on, no idea. I want to exempt recaptcha requests from being proxied. I don't see a global proxy being set, so it's likely your browser add-on is proxying the requests from the browser. If that's the case, maybe there's a way to selectively proxy requests.

Using:
Brave Version 1.73.101 Chromium: 131.0.6778.139.
browser addon v24.11.4 where I clicked connect
Desktop app 1.7.7

@working-name working-name added the question Further information is requested label Dec 20, 2024
@nsrCodes
Copy link
Contributor

we are working on this but there are other things on priority for now

so this might take a while to get shipped, and we will keep this issue open to track it

@wrongsahil
Copy link
Member

Hi @working-name . This isn't supported in the browser level interception right now. We'll try to get this fixed

In the meantime, You can follow the below steps to add some domains to the bypassList for now:

  1. Open chrome://extensions/?id=mdnleldcmiljblolnjhpnblkcekpdkpa
  2. Click on service-worker (This should open the Requestly Extension service worker console).
  3. Run this script
chrome.proxy.settings.get({ incognito: false }, function (config) {
  let newBypassList = config.value.rules?.bypassList || [];
  // Add your domains here
  newBypassList.push(...["example.com", "example1.com"]);
  console.log({ config, newBypassList });
  chrome.proxy.settings.set({
    value: {
      ...config.value,
      rules: {
        ...config.value.rules,
        bypassList: newBypassList,
      },
    },
    scope: "regular",
  });
});

This used chrome.proxy internal api to updated the bypassList domains used by our proxy. Reference

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

No branches or pull requests

3 participants