Maybe Chrome doesn't like the xml file sent in that many packets?
zoomkat
Thanks for responding.
I agree this could be the problem with Chrome. Chrome is definitely layer 2 aware. There may be a bug in the handling of multiple packets in xml files.
I have already looked at the packets and xml file data using Wireshark and I could see the client.println's were generating more packets. I could not see any other difference in the xml data.
I know my code example using client.println's isn't pretty. (and the smiley is some garbage added by the forum coding??)
Anyway it's worth a try to recode using a buffer and
client.write(buf, maxbyte);
to check if Chrome works even though this approach uses lots of Mega 2560 ram.
Z