Initiate third-party login, such as WeChat login.
<code>1.先从a页面进入登录页b,点击微信登录; 2.open一个微信的二维码授权页面c,用户打开应用扫一扫授权; 3.关闭回调后的逻辑处理页c,并将b页面刷新到a页。</code>
Here comes the question. In the third step, the login registration logic is processed on the callback interface of c. How does c control b to refresh to page a before closing. Can't figure it out? ? ?
Add an example: Store No. 1 has this function.
Initiate third-party login, such as WeChat login.
<code>1.先从a页面进入登录页b,点击微信登录; 2.open一个微信的二维码授权页面c,用户打开应用扫一扫授权; 3.关闭回调后的逻辑处理页c,并将b页面刷新到a页。</code>
Here comes the question. In the third step, the login registration logic is processed on the callback interface of c. How does c control b to refresh to page a before closing. Can't figure it out? ? ?
Add an example: No. 1 store has this function.
Page b initiates a request when opening the page and blocks (long connection). When page c is successfully scanned, page b requests the result and jumps to a.
As for implementation, when b requests the server, the server can determine a value (such as session("wechat")). If session("wechat") does not exist, it will block until the scan is completed. If the scan is successful, the url will be returned. If it is rejected, Return the status code to the past), I found that WeChat's scan is implemented in this way.
It’s not difficult to ask the owner. First, when you jump to the login page (b page) anywhere, bring the 'source address' parameter (that is, the a page address), and then after the third-party login returns, call the b page to obtain Just jump to the a page parameters!