>>Just because I type in yourdomain.com does not mean I want you to be able to start playing death metal from my speakers. >Given the way HTTP works, I think i

>>Just because I type in yourdomain.com does not mean I want you to be able to start playing death metal from my speakers. >Given the way HTTP works, I think it kind of does. It means you want the server at yourdomain.com to send you whatever content that URL points to, if anything. I think the issue is really that the client (web browser) shouldn't try to interpret whatever was sent back if it isn't considered safe. In other words, there should be limits of what the browser will do with whatever is send back over HTTP.