Resolve relative OAuth callbacks against the configured application URL

Merged
CL
11d ago
+68-3

Under a long-lived worker, application code can retain a Socialite provider after its request ends. After a successful callback, that provider may return its cached user to a different client without checking the new client’s state or code. Providers created by Socialite now reject user() and redirect() when the active request differs from the one that created them. Reassigning a request also clears the cached user.