"Section 512(a) protects service providers who are passive conduits from liability for copyright infringement, even if infringing traffic passes through their networks. In other words, provided the infringing material is being transmitted at the request of a third party to a designated recipient, is handled by an automated process without human intervention, is NOT MODIFIED IN ANY WAY, and is only temporarily stored on the system, the service provider is not liable for the transmission."
http://en.wikipedia.org/wiki/Online_Copyright_Infringement_L...
https://corp.sonic.net/ceo/2011/08/11/the-five-levels-of-isp...
What you're describing could be any or all of levels 4, 3, or 2.
Our common network software should be designed with the expectation that the middlemen (including your ISP) are actively hostile, and include defenses against their attacks. Making the html stream inaccessible to them is a first step in that direction.
If you can afford a domain, you can afford an SSL certificate...
I have a bunch of domains which, frankly, I don't care enough about to pay money for an SSL certificate for.
I would suggest that an argument could be made for some sort of fraud as well, for not delivering "the internet" (would have to consult with a lawyer to be sure).
Throwing protocol changes and such will not work in the long run, because you're trying to fix this in the wrong problem domain. This is a legal and political issue, not a technical one. If there is a desire to fix this idiocy, time is best spent where it is most effective.
/I suggest political action towards hitting the big ISPs with the Sherman & Clayton Antitrust Acts. These ISPs are patently abusing monopoly power in various ways.
So the ISP is not necessarily interfering in O's contract with A by replacing ads or such -- at least, it doesn't necessarily work that way. I really don't know, some ISPs have been caught replacing content or injecting ads, but in principle the scheme could be managed without doing so.
(My description is from descriptions a few years ago when ISPs were sneakily trying a DPI setup)