Ticket #988 (new defect)

Opened 4 years ago

Last modified 4 years ago

[MapServer-WMS]When "wms_timedefault" is not the same format as the actual data format no error is returned

Reported by: nsavard@mapgears.com Assigned to: assefa
Priority: high Milestone: FUTURE
Component: WMS Server Version: 4.3
Severity: normal Keywords:
Cc:

Description 

No validation is made when "wms_timedefault" format is not corresponding to the
actual data format when a request is sent with the "time" parameter not set in
the  URL request.  A blank image is displayed and the image properties state
that there is an error.

Request sent:

http://server/cgi-bin/mapserv_43?map=/path/to/wms/time_test/htdocs/
wms_time_pattern_test.map&request=GetMap&Version=1.1.1&LAYERS=pattern11&Time=

Fedora Core 2
MS CVS 2004-10-21

Change History

10/22/04 15:43:59 changed by nsavard@mapgears.com 

The same issue arises with "wms_timeformat" parameter.  I set this parameter to
      "wms_timeformat" "%Y-%m-%d %H:%M:%S".  This format is no longer valid for
the "wms_timeformat" parameter.  MapServer is returning data for the following
requests and should instead return an exception:

http://server/cgi-bin/mapserv_43?map=/path/to/time_test/htdocs/wms_time.map&
request=GetMap&Version=1.1.1&LAYERS=time&Time=2004-01-01%2014:10:00

http://server/cgi-bin/mapserv_43?map=/path/to/time_test/htdocs/wms_time.map&
request=GetMap&Version=1.1.1&LAYERS=time&Time=2004-01-01%2014:10

10/25/04 11:08:56 changed by assefa

  • owner changed from mapserverbugs to assefa.
  • milestone set to FUTURE.
Not sure if it shoudl return an exception in this case. For sure It won't be an
OGC exception beccause the time passed by the user is valid. 
  I think the one setting the server should make sure that the wms_timeformat is
of the same pattern as the data. There is no way right now to test the default
time does not match the data.   
 When the wms_timeformat parameters are not valid, all the patters defined in
mapserver will be used (which is the default case). I think it is a valid for
now. We could in the future do validations.

I am tagging this as FUTURE.