theres a security feature in google maps to prevent others from leeching images from the maps database. Google may mistake the multiple connections created from pipelining as an attack on them and will then usually/should ask you for a word verification.

not everyone experiences this

 

still getting problems with maxrequests = 90

interesting.. where'd you hear that? i've never gotten any request for a word verification, either. i don't understand why their server would interpret HTTP pipelining as an attack, however. HTTP pipelining is using the same TCP socket connection, but sending and receiving more than one request at a time. is there a security risk in doing this? it's still one client, one open socket. the data transmitted through that socket shouldn't be relevant, because it's still controlled by their server. if the browser started using parallel TCP connections and opened up 25 different sockets at once, then that might be a little suspicious.

 

i assume that they dont expect users to have pipelining on. :dunno:

Ive only had it come up 2 or 3 times from a 9mbit connection.

I havent had that problem over dsl or on the campus network