Skip to content
This repository has been archived by the owner on Jan 3, 2024. It is now read-only.

Interception behavior(no capture) #662

Open
Ishogbon opened this issue Mar 14, 2023 · 2 comments
Open

Interception behavior(no capture) #662

Ishogbon opened this issue Mar 14, 2023 · 2 comments

Comments

@Ishogbon
Copy link

Ishogbon commented Mar 14, 2023

@wkeeling
Typically, it would make sense that if using an internet proxy with selenium wire, every request passing through the upstream should be intercepted by selenium wire. I noticed chrome was making heavy requests to hostnames *.1e100.net and none were intercepted by selenium wire, and they all pass through the upstream internet proxy.
I'm I missing something, or this is a real issue?

@PatrickVdWillik
Copy link

I'm using selenium wire and chrome using rotating proxies and they work just fine.

What does your code look like?

@awilz10xp
Copy link

awilz10xp commented Aug 11, 2023

@PatrickVdWillik

Here's my script that's not working ... have a local proxy setting managed by my org. Any advice is appreciated.

#702

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

No branches or pull requests

3 participants