error redirect uri mismatch

QQ interconnection this thing, according to the tribe, is really a garbage thing, the official did not make any notice, on the update, ordinarily this is not Shiko, the key is officially updated after, incredibly can not connect, like a discuz forum of tribes, is currently Discuz X3.2 version, has been unable to connect, A use of QQ a health login, prompted redirect URI is illegal (100010) of the

QQ Internet is also the latest bug constantly, causing a lot of users dissatisfaction, from the earlier off the group function, to Release 2.0 interface standards, triggering the chain of webmaster users. And Discuz started from X3, In order to deal with the QQ 2.0 interface standards, the use of the cloud platform to integrate QQ interconnection, that is, users do not have to use the same as before to the QQ interconnection application AppID, but in the cloud platform directly fill in the bindi

About March 2015 low, Tencent QQ Internet development platform adjusted for QQ login application callback address rules, used to repair the QQ login process due to callback address vulnerabilities may lead to the existence of security issues. Bo Master contact with this more, but it is April only to understand this matter, from April onwards, all the new applications of QQ interconnection applications, callback address can not only fill in the root domain name, such as: unvs.cn, this

There is no problem with the code, and the authorization directory has been checked. The most embarrassing problem is the same is open from the browser, if I open from the dialog box link, the payment page can be adjusted, if I enter from the merchant public number, will report Redirect--uri error, this special is very embarrassed ... Has anyone ever had this kin

The previous article was implemented using a global filter, which can also be handled using HttpApplication.Reference article:Http://www.cnblogs.com/dudu/p/aspnet_custom_error.htmlThe first step is exactly the same as the first step in the previous article.The second step starts with:Add this method to the Mvcapplication class in Global.asax: /// ///When an exception occurs, the application is bound to come in here, and when it does, it returns a 404