
HTML code before and after Beeline. Find the differences!Recently, I wrote two articles about Beeline:
Beeline automatically adds a Mail.Ru search toolbar.Beeline automatically adds a toolbar and changes the design of sites.')
At those times, the changes that the telecom operator made had no effect on the performance of the web pages. It was unpleasant, but the sites worked. The second time
a Beeline spokesperson confirmed that there was a “
program error .”
Now the carrier changes the
src attribute on the
iframe tag and the frames stop working!
The story began with what I did the site on which you want to place the frame. The frame added, everything works on the computer, but on the iPad for some reason it does not. It did not take long to think, and after turning on the VPN frame, it worked perfectly, so I concluded that the Beeline telecom operator interferes with the subscriber traffic again and
distorts the traffic .
I found two ways to change the iframe tag:
1. Strange characters
/ m1b3f0rm are added to the src attribute. When I discovered this modification method, I thought a bit and decided to drive the magic symbols into a search engine. The first link was a question on a toaster:
Why does the Iphone add / m1b3f0rm to the address of the frame?Then I decided that maybe I’m in vain blaming the carrier and Apple’s product is to blame, but after I inserted the Beeline sim card into the Android phone, the problem did not disappear.
Original:

After work Beeline:

On the
Google AdSense technical support forum, one of the users writes that Googlebot visits non-existent pages with a line in the link m1b3f0rm. Here the answer is immediately clear: Beeline changes the address of the page, and Google indexes all the pages that users load.
2. Double quotes are added to the src attribute. If the quotes have already been added earlier, then their number doubles and browsers consider the code to be invalid. This happens if the https site is registered in the src attribute.
Original:

After work Beeline:

As you can see, instead of
src = "https://123.abc", now
src = "" https://123.abc "" and the browser considers the attribute invalid. I'm not saying that on every page with a disabled toolbar service, an external script is loaded anyway.