First, we will briefly introduce the tested product. The product is a CS structure consisting of two windows. The B window is embedded with IE and used to access the webpage.
A colleague responded to using our product. After clicking the "tag" field on a page in window B, the subsequent search results page cannot be displayed. However, this problem does not occur on machines of myself and other colleagues. Ask the colleagues to do the following:
Step 1: Ask this colleague to visit the same page in IE and click the "tag" field to find that the page cannot be displayed again. When packet capture is performed using httpwatch and the returned HTTP status code is 403, you can determine that the search page cannot be displayed because of the loading sequence of the page items (JS, CSS) and the operating system/IE version, because 403 indicates: "(Forbidden) The server rejects the request. "
Step 2: Ask your colleagues to ping the CGI domain name in the CMD window to successfully receive the response.
Step 3: Ask your colleagues to access the same page using Firefox and click "tag" to go to the subsequent search page. Combined with step 2, it can be determined that the server does not prohibit access from colleagues' machines. IE cannot access the search page, which may be caused by a special string in the header.
Step 4: Ask your colleagues to copy the User-Agent field value caught in httpwatch and find the "baiduxxx" field in it.
So far, find the cause of the problem. Because the Apache where CGI is searched is configured to prohibit access by crawlers such as Baidu and Google, fuzzy match is used for crawling keyword filtering, this colleague installed "Baidu hard drive search", which added "baiduxxx" to the User-Agent. Solve the problem after the development modifies the filter rule to a full match.
It can be seen that understanding the meaning of the HTTP request response code can more accurately locate the problem