And if you had that level of control anyway, you wouldn't need to spoof attacks against the server, you could just redirect all incoming requests to a different server which returns whatever HTTP response headers or bodies that you want.
So your described attack is highly unlikely to ever happen.
How do you spoof your IP in TCP? If you spoof your source address you shouldn't be able to get past the handshake.
You spoof the IP address you are sending from and then predict the TCP sequence number so you can make it look as though you are receiving the replies (even though they are going to another machine since you spoofed the IP address).
Such an attack was proposed by Hacker News' very own rtm: http://tools.ietf.org/html/rfc1948
My bad, sorry for the noise.
edit: I suppose this means it's time for me to finally discard my copy of Inside TCP/IP, third edition. :-(
I think, a more realistic approach for example would be a ssh honeypot like kippo (https://code.google.com/p/kippo/).
Hate to be a killjoy, but things like this are usually not a good idea. Unfortunately, somebody has to rediscover that every six months or so.
edit: nevermind, I was going off of hilariously out-of-date information. TCP ISNs haven't been easy to predict in -- gulp -- about a decade. Damn, now I feel old.