Possible Arduino 1.0.1 Ethernet Library bug?

Below is the meta refresh code with the refresh delay set to 0. I think it has been mentioned that the get request may be large. I think there is a limit to the number of bytes in a get request. What do the large get request look like?

Zoomkat. Thanks for the meta refresh code. I have had 3 browser instances running on separate machines with no problems. So I've convinced myself that the ethernet library can handle more than one GET at the same time.

I do see problems when the GETs are larger and the GET processing time is longer. An example of a larger GET is

GET / HTTP/1.1
Accept: */*
Accept-Language: en-au
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Host: www.google.com
Connection: Keep-Alive
Cookie: PREF=ID=cf8225e786102cae:U=aed0bd2767ce0d28:FF=0:LD=en:TM=1344669948:LM=1344675567:GM=1:S=efYEyXMAzONP9vmm; NID=62=nzvUvw-uwLPuS3o_XvNjrFY4eF8wy9V1tk9-TnNGU1wqgV00bvah3M9bQ2dwTiVk1XdzursfpRMIFlCjEqnM7kzGMkGnCo0mneVKh-7bo7bTDXd5otBN0WXDjL8OMK_3x5cb16840MCJ63qsPX_-ukLTTBwEC_eXJA8KTyardwt_5oF38MFrOTHve-U; SID=DQAAALYAAACA5RsEr9jpPeHdkU-fEX_LRYJfYtxuYUm0g2tUOLzGs3s8aSM6gkMQnSFroINbt0_-0xht0hy1W6f34gWN5BFLNwoFdHNYiqGB_GHC3u_4nxqi-iEO1qpZGj4AVUtitmyXw79A2CbZEp5cCXa_-2CV7Pcw-NYQINkQTC8whE_h4Tmwcx4mTkxmh2f2h8398xXq6n1FFT692TAgzgZql23cgIHvgMx4RX_-3EUBYj-9wZbdy7B_W6f134b8w-txvXc; HSID=ASgvaKS8_05lPlNx2; APISID=IXZ_W0bGBXpKKKNV/Ah-26fBu0IZEhjEhf

This the sort of GET IE generates at times !!!! and I think these cause problems for the ethernet library.

I have a question about the handling of client.stop()

In many ethernet library examples there is a chunk of code

    // give the web browser time to receive the data
    delay(1);
    // close the connection:
    client.stop();

What is the real purpose of the delay(1) ? How is the length of the delay required calculated ? And what happens if the delay is not enough??

It seems to me like a very crude way to handle waiting for the W5100 TX buffer to clear.