Applet referer

How the applet is based on referer Jump to different background environments

This article mainly explains “ How the applet is based on referer Jump to different background environments ”, The explanation in the text is simple and clear , Easy to learn and understand , Next, please follow Xiaobian's ideas and go deeper slowly , Study and learn together “ How the applet is based on referer Jump to different background environments ” Well ！

One 、 problem ：
When developing small programs 4 A version （ Development 、 Experience 、 to examine 、 formal ）. So different environments require different backgrounds . Especially the audit version , Because wechat audit is also required , If the request is wrong , It's going to fail . Because the production environment corresponds to the old background version , Therefore, the approval version cannot be transferred to the background production environment , You can't jump to the development environment .
For the convenience of production 、 to examine 2 Each version of the applet requests /prod. Here, it is necessary to distinguish between the real request and the production request 、 Where did the audit come from .

Two 、 Solutions .
Wechat sends requests to our servers wx.request I'll take one with me referer Of header Parameters . The format is as follows ：

https://servicewechat.com///page-frame.html

among <appId> It's the applet that sends the request appId,<version> It's the version of the applet .

Development 、 Experience 、 to examine In the version version The value is 0, Development tools version The value is devtools.
The official version of version Value is greater than 0 The positive integer , Indicates how many times the applet has been released to the official version . Examples are as follows ：

 Development Edition ：
https://servicewechat.com/ Applet appId/0/page-frame.html
 Experience version ：
https://servicewechat.com/ Applet appId/0/page-frame.html
devtools：
https://servicewechat.com/ Applet appId/devtools/page-frame.html
 Official version ：
https://servicewechat.com/ Applet appId/6/page-frame.html

3、 ... and 、 Solution . adopt nginx Make server selection .
1、 Define a variable foo, To configure a map, hold http_referer Mapping to foo.

map $http_referer $foo {
    
	default   "prod";
	~^https://servicewechat.com/[^/]+/0/(.*)$ "dev";
	~^https://servicewechat.com/[^/]+/devtools/(.*)$ "dev";
}

2、 Configure server .

upstream dev {
    
     server localhost:7777;
}
upstream prod {
    
    server localhost:9999;
}

3、location Use in foo Variable , Navigate to the correct address .
Here I use add_header hold foo Variable output , As a test .

   location / {
    
        #set $foo "$http_referer";
        add_header wkfoo 'foo: $foo "$http_referer"';
        proxy_pass   http://$foo;
    }

4、 Test it .

curl -H 'Cache-Control: no-cache' -I "https://xxx.xxx.com/prod/xxx? Parameters 1=xxx& Parameters 2=xxx" --referer "https://servicewechat.com/xxx/devtools/page-frame.html"
curl -H 'Cache-Control: no-cache' -I "https://xxx.xxx.com/prod/xxx? Parameters 1=xxx& Parameters 2=xxx" --referer "https://servicewechat.com/xxx/0/page-frame.html"

Is it necessary to set the applet referer？

It seems that unless you open a web page in an applet And the applet can't bring it automatically cookie token It seems that you can't be attacked ？