CDN Optimizing HTML On the Fly

Caerdwyn writes "Cotendo, which is a content distribution network, has taken to altering HTML as it passes through their CDN to optimize web pages for faster rendering. This is essentially a repackaging of the Apache mod mod_pagespeed (from Google), with the critical difference being that the rewriting of HTML occurs inline rather than at the web server. We all know that well-written HTML can result in much better rendering of whatever your content is; the questions are 'Will this automatic rewriting cause other problems, i.e. browser quirks?' and 'Assuming that only the web pages of Cotendo's customers are altered, are there nonetheless potential legal troubles with someone rewriting HTML before delivery to a browser?'"

Legal precedent

[rumith]

It doesn't really matter if it's a technically good move; if this sticks, we might be getting lots of ISP-inserted ads, iframed toolbars and other "value-added" stuff in non-encrypted HTTP traffic pretty soon.

My content how it was intended

[Pikoro]

If I write a web page, however much it sucks, that's exactly how it should be delivered.

If I see a bad website that takes 20 minutes to load, then I will never buy anything from that site or it's company. If they can't hire a decent web programmer, they don't deserve my money.

However, if you change the page to make it render faster, the ISP is lying FOR the shitty company and their shitty website by making it appear to be a well crafted site.

tl;dr: Leave the shit shitty. It'll put bad programmers out of business which we need.

Legal troubles?

[cerberusss]

the questions are 'Will this automatic rewriting cause other problems, i.e. browser quirks?' and 'Assuming that only the web pages of Cotendo's customers are altered, are there nonetheless potential legal troubles with someone rewriting HTML before delivery to a browser?'

I couldn't give a rat's ass about legal troubles. Slashdot is still a tech forum, right?

There are LOADS of much more interesting questions to ponder, such as: what is exactly the speed improvement? And does it work for Javascript and CSS too? And wouldn't it be much better to work on images instead? Or is that too computationally intensive? What kind of algorithm do they use? In what language is it implemented? Et cetera. Legal troubles shmegal smougles.

Re:Legal precedent

[rumith]

I think you missed the point in your rush to object. What's the legal difference (IANAL) between optimizing HTML and inserting ads? In both cases X leaves the source, Y arrives at the destination. Opera does something like this for their Opera Mini browser: the content that is delivered to the browser isn't even HTML, it's some proprietary format, although the browser usually correctly renders it to what the HTML would look like. However, in case of Opera Mini, I explicitly agree to such manipulations and to accompanying technical solutions.
Once again, this may be a good move on Cotendo's part that will lower their costs and improve end user experience, but it is a dangerous one, because if ISPs and CDNs automatically receive the right to manipulate transmitted content however they please, it will certainly lead to abuse in some cases.

Re:Legal precedent

[WrongSizeGlass]

Though I agree with your point, what about the other side of the coin: CDN's service removing content from a page being delivered such as an infection? Could this be used to strip those nasty javascript code injections or Flash-based shenanigans from an infected site 'on the fly'? Removing infections would be as 'good' as inserting ads, toolbars, etc is 'bad'.