Response Checker

This application offers incredibly easy functionality. Let’s say that we have a database on hyperlinks. We give this database to the application, and it’s going to send a request for each of them (one can choose one of the following types of the request: HEAD/GET/POST), checks the coder in the HTTP-response and puts the link into a file with the corresponding code. Such method allows quick sorting of the database into separate groups for links with 400 response code, for missing links with 404 response code, for links with redirect etc. If the link gives no response during the predefined period of time, such link is going to be put into "Error file".

Main advantages of my application:

  • The size is 3Mb (however, one can find solutions, which are 10 times lighter)
  • It doesn’t require any frameworks or libraries
  • The interface has no excessive elements
  • One can choose any desired time-out period
  • One is able to set a delay between the requests in the thread
  • It"s possible to set the number of threads
  • One can set the amount of bytes in the response
  • One can use the following request protocols: HEAD/GET/POST


Response Checker (Fig. 1. About the application) Response Checker (Fig. 2. Appearance during the first launch. In order to show "Settings" form one has to press F3 or use the following items in the main menu: Menu/Settings/Show Settings Form The second (red) parameter is used to indicate the name of the file for analysis) Response Checker (Fig. 3. After changing any of the settings one has to apply them! In order to do that it’s required to press F4 or use the following items of the main menu: Menu/Settings/Set Current (this screenshot was made already when the settings were applied and the process of analyzing has been launched)) Response Checker (Fig. 4. The process is being carried out. The progress bar is used to show the current number of active thread. The counter is used to show the total number of processed links) Response Checker (Fig. 5. The progress bar indication may change rapidly, because the first threads are just sending the request, the second are simply waiting and the third are cancelling the request because of the time-out...) Response Checker (Fig. 6. The sorting process has been successfully completed) Response Checker (Fig. 7. That’s an example of the final result. Each possible type of server response will correspond with a separate file. The file name is created using the following model [source name]-[server response code].txt)

Important! Depending on the configuration of your system (network adapter, internet provider and DNS in use) the number of threads may affect the quality of responses. In other words, the higher is the number of threads, more links will be added into the "Error" file. I used no limits during the testing procedure, and my testing computer is an average, so you are free to make experiments and share your experience.