You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way that it currently handles intercepting is to turn the proxy on when you switch to the tab defined as a proxy tab, when you switch out it turns the proxy off.
The bug is that if you switch to a proxy tab but other tabs are sending off background data (ie: ajax posts to an api) it will get captured because you are in a proxy tab context.
Unfortunately the proxy API is browser wide so I need to find a workaround to ignore traffic from other tabs.
Current working theory: using the WebRequest api to intercept all traffic when in a proxied tab, and if it's not from the proxy tab, disable proxy for that request, then re-enable it afterwards
The text was updated successfully, but these errors were encountered:
The way that it currently handles intercepting is to turn the proxy on when you switch to the tab defined as a proxy tab, when you switch out it turns the proxy off.
The bug is that if you switch to a proxy tab but other tabs are sending off background data (ie: ajax posts to an api) it will get captured because you are in a proxy tab context.
Unfortunately the proxy API is browser wide so I need to find a workaround to ignore traffic from other tabs.
Current working theory: using the WebRequest api to intercept all traffic when in a proxied tab, and if it's not from the proxy tab, disable proxy for that request, then re-enable it afterwards
The text was updated successfully, but these errors were encountered: