1. When building a PC authorization link for a WeChat third-party platform, opening it directly throws an error: Error Please confirm that the domain of the authorization entry page is the same as the domain of the post-authorization callback page, and that both must be identical to the authorization initiation page domain filled in when applying for the third-party platform. Domain of the authorization entry page: empty. See Figure 1.
2. In the existing implemented program, opening the authorization entry page first and then redirecting to the PC authorization link does not throw an error, and the QR code to be scanned displays normally. Carefully comparing the differences between the two, the page that displays the QR code normally includes referer in its request headers. See Figure 2.
3. Carefully comparing the differences between the two, the page that displays the QR code normally includes referer in its request headers. The page that throws the error does not include referer. See Figure 3.
4. Official documentation: A third-party platform service provider builds an authorization link and places it on its own website; when a user clicks it, the authorization page pops up. I decided to place the PC authorization link under the authorization initiation page domain. I added the link at http://console.dev.chinamcloud.cn/ccpauth. See Figure 4.
<a href="https://mp.weixin.qq.com/cgi-bin/componentloginpage?component_appid=wxd98c58b273d21bdf&pre_auth_code=preauthcode@@@V8lWmb5dQYkVfJL8wUOKPWyN9ZMhT-n8cOz7B7xxHkqth3QPamJJpsbk5Q6lwgxs7y49-H_zefIjQdM8IECPVw&redirect_uri=https://console.dev.chinamcloud.cn/ccpauth&auth_type=1">PC端授权链接</a>5. Right-click the PC authorization link and open it in a new tab. No error is thrown, the QR code to be scanned displays normally, and its request headers include referer. See Figure 5.
6. View HTTP Headers -> Referer on MDN Web Docs. The Referer request header contains the address of the source page of the current request page, meaning the current page was accessed via a link from this source page. See Figure 6.
