Analyzing the Scan Result
The most important statistical data about the scan are shown in the overview, marked in orange, near the top of the window. Below the orange-marked overview, various scan result details can be selected.
The search form, on the right side near the scan result detail selection, allows you to search for an ASCII text fragment overall web pages of the scan result. By default, the text fragment is searched for within all HTTP request headers, all HTTP response headers, and all HTTP response content data.
The remove URL form, which is shown below the scan result detail selection, allows you to remove specific sets of URLs from the scan result. The set of removed URLs is selected by the received MIME type (examples: IMAGE/GIF, APPLICATION/PDF, ..), and linked with a logical AND condition with the received HTTP status code for the URLs (200, 302, ..), or with a Page Scanner error code, such as "network connection failed".
| selects a specific MIME type). The input field is case insensitive (upper and lower case characters will be processed as identical). any means that all MIME types are selected, independent of their value. none means that only URL calls whose HTTP response headers do NOT contain MIME type information (HTTP response header field "Content-Type" not set) will be selected. |
| selects an HTTP status code or a Page Scanner error code. |
Note: A few URLs with excluded content types may flow into the scan result (not selected by scan input parameter). You can use the "remove URL" form to clean up the scan result, and to remove any unwanted URLs. The most common case is to remove PDF documents from the scan result.
Scan Result Details
The Scan Input Parameter displays all input parameters for the scan (without authentication data).
Scan Statistic displays some additional statistical data about the scan. Similar Web Pages are the number of web pages with duplicate content (same content but different URL path). Failed URL Calls are the number of URL calls which failed, such that no HTTP status code was available (no response received from a web server), or that the received HTTP status was an error code (400..599).
Non-Processed Web Servers displays a summary of all web servers which have been found in hyperlinks, but whose web pages or page elements have not been scanned. The number before the server name shows the number of times the hyperlink was ignored by Page Scanner.
Scan Result per Web Page: displays all scanned web pages. The embedded content of a web page, such as images, is always displayed in a Web Browser Cached View. For example, this can mean that a particular (unique) image is only shown once inside the web page in which it has been referenced for the first time. All subsequent web pages will not show the same embedded content. This behavior is more or less equal to what a web browser does - it caches duplicate references over all web pages within a web surfing session.
More details about a specific URL call can be shown by clicking on the corresponding URL hyperlink.
Broken Links displays a list of all broken hyperlinks.
Duplicated Content displays a list of URLs with duplicate content (same content but different URL path).
Largest Web Pages displays a list of the largest web pages.
Slowest Web Pages display a list of the slowest web pages.
Tip: you can click the bars to display the corresponding page details.
Converting a Scan Result into a Web Surfing Session
A Page Scanner result can be converted into a “normal” web surfing session, which can be used to create a load test program.
Input Fields
| The filename of the web surfing session. You must enter a "simple" filename, with no path and no file extension. The file extension is always | |
| allows you to select the scanned web pages which should flow into the web surfing session. “All Pages” means that all scanned web pages are selected. Alternatively, the option “Page Ranges” allows you to select one or several ranges of page numbers. If you use several ranges, they must be separated by commas. | Example: "1, 3-5, 7, 38-81" |
| limits the number of URL calls that should flow into the web surfing session. |
|
Tip: Apica recommends not converting more than 1,000 URL calls into a web surfing session.
| we recommend that you enter a short comment about the web surfing session. |
| also loads the web surfing session into the transient memory area of the main menu, or into a scratch area of the Session Cutter. |
After the web surfing session has been stored, it will be automatically loaded into the Main Menu if the “Load Session into” checkbox was selected. After this, you can generate the load test program.
Can't find what you're looking for? Send an E-mail to support@apica.io