A. No-transform Agreement
The No-transform protocol supported by TC is in the following two forms: A. Cache-control is explicitly declared as No-transform in HTTP response. B. The meta tag explicitly declares Cache-control as No-tranform, in the format:
B. Handheld Agreement
The page explicitly specifies the WAP Web page through the <link> tag, with the following declaration format: <link rel= "alternate" type= "Application/vnd.wap.xhtml+xml" media= "handheld" href= "target"/> such as third-party sites do not want the page to be transcoded, you can add this agreement, inform us that the original Web page should have a WAP version of the page, when users enter the third party site, the first to enter the center prompt page, so that users choose to jump to the original page or third-party website own WAP page.
C. User-agent Related TC Crawl page, the use of User-agent is: mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Baidu Transcoder;) If the third-party site does not want to transcode HTML pages, and can provide the corresponding WAP page, then you can return to their own WAP page according to this user-agent, while in the HTTP Response Display statement: Content-type: Vnd.wap.xhtml+xml, then TC will not transcode this page, but directly jump to the corresponding WAP page.
Joe uses the first kind of no-transform protocol, by adding a statement in the head tag to prohibit Baidu to transcode the site, we can choose the right way to achieve the desired effect. For the use of WordPress friends, you can use mobilepress this plugin, Joe thought is still good, Joe also on the plug-in console has been Chinese, and the theme of the font to some optimization, Everyone is interested to see: WordPress Mobile Plugin Mobilepress optimized version of the free download
Website how to prohibit Baidu transcoding