There is literally no reason to keep the UserAgent string up to date or any particular version. The entire point of it, in this case, is just to ensure that what the site returns to WebParser is the same thing the site returns to a reasonably modern browser. It just makes it easier to be sure everyone is on the same page (pun intended) when there are problems we are trying to solve.thohan wrote: ↑August 2nd, 2020, 9:02 pm I was looking at the new Pollen files and noticed that the UserAgent was for Firefox 78 while my browser was on 79 (I assume jsmorley 's is also updated) and this started me thinking the a variable #userAgent# in the WeatherComJSONVariables.inc file might be a good idea.
Between the expanding number of .inc files, the possibility of a security problem in a specific version of the browser, and just wanting to keep the userAgent up to date with the latest and greatest version being used by the user I think that this might be a way to set up for an easy fix in the future if this problem arose.
in any case I am simply agog and appreciative of al the work and problem solving involved in getting the weather feed up and running. This makes my transition from DarkSky to weather.com much easier and I thank you.
I actually think this was more relevant when we were parsing the embedded JSON from the actual website. Now that we are getting the JSON directly, well, JSON is JSON isn't it... I'm not entirely sure that that UserAgent option still serves any useful purpose, although it certainly can't hurt.
However, fair enough. I'm not opposed in principle to centralizing where that value is stored, and will likely take your advice the next time I update things. That way, if you do want to change it for some reason, you will only have to do it one place.