[Improvement] Better OAuth 2.0 redirect handling

This issue is a result of the discussion happening on #404

Improvement 1 – Also intercept redirects

The current implementation of the auth window only looks at window location changes. So, if the auth form redirects to a URL that then redirects somewhere else, Insomnia will only see the final URL in the chain – the one that ends up getting loaded by the browser window.

It looks like Electron BrowserWindow has an API that allows inspecting redirects directly.

Improvement 2 – Option to enable strict redirect_uri matching (currently the default)

Because of #396, Insomnia makes sure the redirect URL is prefixed with the redirect_uri defined in the OAuth settings. However, this has proved to cause problems for some users. It’s also possible that Improvement 1 will solve this problem instead.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Logifire]

I have the issue with the Blizzard API (https://develop.battle.net/documentation/api-reference/oauth-api), it’s my first time trying OAuth, and couldn’t understand where the “code” was. It’s a query parameter of the redirect back to the original site - but Insomnia didn’t show it in the timeline.

Could also be nice showing the URL the preview window is displaying - after redirects, that’s how I figured it out, using a normal browser.

EDIT: I was a bit to fast, I thought this was blocking me, I didn’t used the built in OAuth 2, I was trying to follow the flow (see link above) doing individuel requests, and couldn’t find the “authorization code”.