- From: Luca Passani <luca.passani@gmail.com>
- Date: Mon, 18 Jan 2010 10:45:24 +0100
- To: MWI BPWG Public <public-bpwg@w3.org>
As blog comments suggest, this has happened with other users and always within a mobile context (m.facebook.com, Roger Wireless in Canada). Anyway, I wrote that this is not the definitive proof that a transcoder is involved, but just that it is not unlikely that a transcoder is the problem here. Luca Sangwhan Moon wrote: > Not sure why fingers are pointing at transcoders here. A > malfunctioning reverse proxy, which can exist in a non-mobile context > (i.e. load balancing) could as well have the exact same effect. > > Cheers, > Sangwhan > > On 2010/01/18, at 6:07 PM, Luca Passani wrote: > >> While I don't have definitive proof that a transcoder is to blame >> here, this article definitely smells like one is involved. >> >> You guys should think carefully about what you do when you legitimize >> transcoders. Web access to gmail, facebook or even your netbank can >> be at the mercy of what some programmer in israel, silicon valley or >> chicago has been drinking on a certain evening 8 months earlier.... >> >> Luca >> >> -------- Original Message -------- >> Subject: [wmlprogramming] Transcoder? >> Date: Mon, 18 Jan 2010 03:34:00 +0100 >> >> >> >> >> >> >> >> >> >> >> >> This one definitely seems a rogue transcoder: >> http://www.boston.com/business/technology/articles/2010/01/15/ap_exclusive_network_flaw_causes_scary_web_error/ >> >> >> djn >> >> >> >> > > -- > Sangwhan Moon <smoon@opera.com>, Opera Software ASA > Skype: innodb1 | Mobile: +372-5971-6147 >
Received on Monday, 18 January 2010 09:45:55 UTC