Not all the local pages have this issue, so it may simply be a question of the last time the page, as distinguished from the content, was rebuilt; the Forecast Discussion, where I first found the problem, is pretty static — they just keep pushing new versions to the top and old ones fall off after a couple of days. Other pages that might require the occasional reformat do not so suffer.

And I suppose hiding the error message down there where only the geeks will find it is probably a Good Thing in the long run.

I suspect the server at forecast.weather.gov is actually located at NWSHQ, but that the CMS that generates forecast pages looks for a code tag that tells it what actual address to display.

Since the same message appears on the page for the Atlanta forecast discussion, I’d say the problem is on the server in Silver Spring.

I figure it’s unlikely I’d get malware from my campus webmail. And if I do, I know the person to go and hassle about it. But it is kind of embarrassing for an organization to have mess-ups of that sort (though certainly more for the NWS, who are supposed to know about things like geography.)