You have a Web page that uses the BASE tag to specify the base URL of the Web page. The base URL is used to resolve the relative links and references. However, if users access this Web page by using Windows Internet Explorer 8, you find that the "Page Loading Time" value increases exponentially.
If you use tools such as Network Monitor to monitor the network trace when this issue occurs, you notice that Internet Explorer 8 does not send the request to the URL that is specified in the BASE tag. Instead, Internet Explorer 8 sends many requests to the URL of the Web page. For example, assume that the URL of the Web page is http://webserver/test1/test2, and the URL that is specified in the BASE tag is http://webserver/test1. In this example, Internet Explorer is expected to send a request to http://webserver/test1 to load the resources. However, Internet Explorer 8 sends many requests to http://webserver/test1/test2 instead. Additionally, Internet Explorer 8 opens many parallel HTTP connections to the Web server.
Note After a while, Internet Explorer 8 recovers from this issue and sends the request to the correct URL. Therefore, the page is eventually loaded and rendered. However, this problem creates unnecessary server requests, and it consumes lots of resources on the server and on client computers.
If you use tools such as Network Monitor to monitor the network trace when this issue occurs, you notice that Internet Explorer 8 does not send the request to the URL that is specified in the BASE tag. Instead, Internet Explorer 8 sends many requests to the URL of the Web page. For example, assume that the URL of the Web page is http://webserver/test1/test2, and the URL that is specified in the BASE tag is http://webserver/test1. In this example, Internet Explorer is expected to send a request to http://webserver/test1 to load the resources. However, Internet Explorer 8 sends many requests to http://webserver/test1/test2 instead. Additionally, Internet Explorer 8 opens many parallel HTTP connections to the Web server.
Note After a while, Internet Explorer 8 recovers from this issue and sends the request to the correct URL. Therefore, the page is eventually loaded and rendered. However, this problem creates unnecessary server requests, and it consumes lots of resources on the server and on client computers.