Skip to content

Support for Different Domains #32

@aronduby

Description

@aronduby

Is your feature request related to a problem? Please describe.
If you are working on an app that makes calls to an API on a different domain you have to open a tab for that domain and enable debugging on that and then go back to the tab with your app. But that means extra tabs and extra steps and not having the clear visual if its on or off anymore since it's enabled on a different tab.

Describe the solution you'd like
My favorite thing would be turning it on for the current tab would apply to all requests in the tab, not just the same domain, but I could imagine some decent arguments popping up against such a blanket application. So I think a a domain whitelist could also work well without casting such a wide shadow.

Describe alternatives you've considered
I described my work around in the problem description.

Additional context
I run into this all the time when working on SPA that runs locally for dev making calls to a remote API server that I'm SSH'ed into for port forwarding. You forget its on and get concerned about why everything seems to be running so slowly. Or the even worse example when requests start completely stalling out of nowhere and after a bunch of wasted time you realize that a co-worker has started a debug tunnel on the server and a tab you haven't looked at in days that's tucked away in a purgatory of a tab group still had this enabled but the tab with the actual app did not.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions