For the most recent 12306 service end plug-in (cut DNS, cutting station) killer, there is a better solution. This article is the last to share, take a few years of research experience to do a summary.
12306 Ultimate Killer
- 12306 made some major changes last week and implemented plug-ins on the server
- Within a certain time: cut different stations, cut different DNS, pop "query failed", automatically kicked out
- No plug-ins, manually slightly change the station query will also be kicked
- Basically blocked all of the existing plugins
Solutions and principles
- (Chrome) in the background with IFRAME or Ajax check the status of the login, non-login automatic OCR Login
- Fishlee Scenario: Enable 6 anonymous queries, one more formal query
- My program (FIREFOX):
- After logging in, save the user Cookie:jsessionid first.
- Then clear the cookie, which is the equivalent of quitting
- Swipe ticket, equivalent to using anonymous cookie query
- When the ticket is checked, it is intercepted before the automatic submission, and the login user Jsessionid is assigned a cookie.
- Equivalent to the final order submission using the original login account
Results 1:chrome Unattended Plugin
- Based on the previous article, "Share 12306 automatic Verification Code identification submission, Spring Festival ticket Preparation"
- Latest added: Add IFRAME timer refresh at the bottom of the page, automatic OCR login in case of being kicked out
- Latest version download:Http://pan.baidu.com/s/1qWLnq1I
- Currently only supports Chrome's higher version
- Can be combined with the previous article "Share 12,306 second ticket experience and killer"
- Reference article 2: Baidu "Chome Manifest.json embed"
results 2:firefox seconds ticket plugin
- Based on the previous article "Share 12,306 second ticket killer source code"
- If you keep cutting DNS, cut the station, will be kicked in seconds
- Latest added: So join anonymous query, check the ticket to use the real identity
- Latest version download:Http://pan.baidu.com/s/1i39WoLZ
- Only Firefox is currently supported
- For more functions, please refer to "Sharing 12,306 second ticket killer source code"
written in the last
- This is the final article, because of the individual amateur research only, and powerless, so later do not provide follow-up maintenance and support
- This is suitable for programmers, need to customize and modify their own, otherwise it is difficult to fit your needs
- If you do not know the principle of the source code, such as: Results 2 if not in the login page, but in the ticket page to log in, there will be problems, you can see the source code to improve
- The best use of bbs.fishlee.net and "Little Fish", these 2 have been updated and maintained, and can be found in its forum some spider silk Horse traces
-
123,061 straight in perfect, has no absolute seconds to kill artifact, but I believe that the ox is walking back door ...
written in the last-my experience 1: simultaneous deployment 6, 7 results 1-chrome, to carry out unattended ticket, it is best to use different dns/hosts, 5 minutes before the start of the brush ticket
written in the last- my experience 2: on The above basis, using the results 2-firefox (cut DNS, cut station), manual operation of the second ticket, 10 seconds before the start of the brush ticket
Share 12306 tips for robbing a ticket-final article
