If I recall correctly, we started doing this when weather.com started some shenanigans and changing their HTML's "scrape-ability" by detecting user agents but DID NOT do those same shenanigans if your user agent was a mobile browser. Eventually they stopped this, but we kept the user agent to ensure the shenanigans would not return.I just can't remember the exact reason why we decided to use a browser user agent for the weather.com skins at the time we were building them. It might have been simply for the "peace of mind" that the site won't reject our requests, or even a remnant from the time when we used to parse the entire weather.com page instead of just the .json request...
Probably not needed now at all since we transitioned to using their API, but best to not poke the bear at this point.
Statistics: Posted by SilverAzide — Yesterday, 10:23 pm