which is correct and returns a map image. The second map request supplies a COLORSCALERANGE parameter, the first does not. This is probably because this portal doesn't select a COLORSCALERANGE until the dataset is set.; I would guess the first, misformatted, map request goes out before the information needed to set a dataset is retreived from the database.
This issue is not user visible - the time between the bad request and the good request is pretty quick - but does show up in our logs as 400 errors, including alerts if enough people visit the PRISM portal at once.
The PRISM portal, upon initial load, send this map request:
https://services.pacificclimate.org/ncwms-mm-rproxy/dynamic/x?LAYERS=pr_mon_PRISM_historical_19700101-20001231_bc%2Fpr&TRANSPARENT=true&TIME=1985-06-30&STYLES=default%2Foccam-inv&LOGSCALE=true&NUMCOLORBANDS=249&VERSION=1.1.1&SRS=EPSG%3A3005&SERVICE=WMS&REQUEST=GetMap&FORMAT=image%2Fpng&BBOX=-236114,41654.75,1763886,2041654.75&WIDTH=512&HEIGHT=512
which returns a 400. Very shortly thereafter, it sends this map request:
https://services.pacificclimate.org/ncwms-mm-rproxy/dynamic/x?LAYERS=pr_mon_PRISM_historical_19700101-20001231_bc%2Fpr&TRANSPARENT=true&TIME=1985-06-30&STYLES=default%2Foccam-inv&LOGSCALE=true&NUMCOLORBANDS=249&VERSION=1.1.1&SRS=EPSG%3A3005&SERVICE=WMS&REQUEST=GetMap&FORMAT=image%2Fpng&COLORSCALERANGE=1%2C2000&BBOX=-236114,41654.75,1763886,2041654.75&WIDTH=512&HEIGHT=512
which is correct and returns a map image. The second map request supplies a
COLORSCALERANGEparameter, the first does not. This is probably because this portal doesn't select a COLORSCALERANGE until the dataset is set.; I would guess the first, misformatted, map request goes out before the information needed to set a dataset is retreived from the database.This issue is not user visible - the time between the bad request and the good request is pretty quick - but does show up in our logs as 400 errors, including alerts if enough people visit the PRISM portal at once.