Hi Roberto, Sorry for not having had the time to answer this. I'm more than busy finishing all the details of my trip to FOSDEM 2005. I'll post a detailed answer before I depart If I have the time. Meta-refresh causes problems to regular users. It can also be easily abused (for instance auto reloading advertising), it is troublesome for people that have set connect on demand. It's a big problem for consumers with dialups or ISPs that collect cash on a per KB or MB basis. When on limited bandwith it consumes scarce resources. There's also a great incentive to abuse meta-refresh for sites that get their revenues on a per-click basis for advertising. There's a security problem too. A meta refresh is taken as it was a click from the user, so it can be taken advantage off in a way it'd be unwise to describe in a public forum. ;) AFAIK, there's no standard that specifies what meta-refresh does and how. So it must be implemented "by ear". OTOH, I can perfectly understand its uses on an embedded scenery. As a matter of fact I developed this a couple of years ago for a company needing it for an embedded app. A meta-refresh patch is small and almost no bloat, so maybe having it as a 'configure' option for embedded developers that know what they're doing could be considered. FWIW, I decided not to make it public long ago because some packagers were just picking up patches from the net and making them available to users that were even more unaware than the packager! :-) More interesting facts and concerns can be found in the W3C's original thread: http://lists.w3.org/Archives/Public/www-html/2000Feb/thread.html#232 After considering all these facts (and maybe more), a good solution may come. -- Cheers Jorge.- PS: I ended writing the detailed answer. :)