#2331 closed defect (fixed)
Mapserver 5 doesn't appear to recognise WEB object's minscale (or maxscale) property on the fly
| Reported by: | gwatmuff1 | Owned by: | sdlime |
|---|---|---|---|
| Priority: | highest | Milestone: | 5.0.1 release |
| Component: | MapServer C Library | Version: | 5.0 |
| Severity: | blocker | Keywords: | web minscale maxscale |
| Cc: |
Description (last modified by )
Mapserver 5 doesn't appear to recognise WEB object's minscale (or maxscale) property on the fly? Mapserver 4x did.
URLs:
..&map_web_minscale=250000&...
MS 5 now gives following error:
loadWeb(): Unknown identifier. Parsing error near (250000):(line 1) (expected)
But:
..&map_web=MINSCALE+250000&... or ..&map.web=MINSCALE+250000&...
OR
..&map_web=MINSCALEDENOM+250000&... or ..&map.web=MINSCALEDENOM+250000&...
MS 5 also gives this error:
loadWeb(): Unknown identifier. Parsing error near (MINSCALE):(line 1)
OR
loadWeb(): Unknown identifier. Parsing error near (MINSCALEDENOM):(line 1)
And:
..&map.web=IMAGEPATH+/path/+MINSCALE+250000&...
MS 5 also gives same error:
loadWeb(): Unknown identifier. Parsing error near (MINSCALE):(line 1)
Has the map scale control been shifted to another object - can't find this in the docs?
Change History (5)
comment:1 by , 17 years ago
| Milestone: | → 5.0.1 release |
|---|---|
| Owner: | changed from to |
comment:2 by , 16 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I was pretty conservative in what to allow via URL. That said, I don't think there is much, if any, risk with allowing access to that parameter. I've re-enabled in the 5.0 branch and in the trunk. I need someone to rebuild maplexer.c and commit though since anything I do on Mac OS seems to cause problems.
Steve
comment:4 by , 16 years ago
Doh! I meant to generate a new maplexer.c for you and then I forgot. As a result, 5.0.1 has been released without an updated maplexer.c and that caused the build to break for some users.
I have committed a new maplexer.c generated with flex 2.5.31/Linux to branch-5-0 in r7312. Once I get confirmation from the users who reported the problem that the new file solves the issue then we may have to release 5.0.2.
Steve, it seems that MINSCALE/MINSCALEDENOM and MAXSCALE/MAXSCALEDENOM are not enabled for URL_STRING mode in maplexer.l.
Should they be added to URL_STRING mode or were they kept disabled intentionally to prevent clients from requesting layers/maps at scales at which the service provider do not want to offer them for performance or other reasons?