Ticket #962 (reopened defect)

Opened 4 years ago

Last modified 4 years ago

[MapServer-wms]Invalid number of digits for the time parameter doesn't output a map or return an error

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

Description 

When a GetMap request is issued with a time parameter set to a time value that
contains invalid number of digits for one of the time measure (YYYY or MM or DD
or  hh or mm or ss), no map or no error is returned.  The image properties state
that the image cannot be displayed because it contains error.

Example of a request:

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%201434:10:00

Found on Fedora Core 2

Change History

10/15/04 10:08:01 changed by nsavard@mapgears.com

  • bug_file_loc set to assefa@dmsolutions.ca.

10/18/04 10:23:24 changed by assefa 

Checking this ... The specs specfies that a service exception should be 
returned in this case when the time value is invalid (section c5.1 in wms 
1.1.1)

10/18/04 13:07:31 changed by assefa

  • status changed from new to closed.
  • resolution set to fixed.
Corrected in mapwms r1.120.

If the time given is invalid, It will use the default time set. If there is no 
default time, an exception is returned. 
If the default time is invalid (and there is no time given) an exception is 
returned.
if the time given is invalid and the defulat time is invalid too, an exception 
is returned.

10/18/04 18:24:30 changed by assefa

  • status changed from closed to reopened.
  • resolution deleted.
  • milestone set to FUTURE.
Note that Time=2004-01-01%201434:10:00  is parsed properly by the regex time
parser "properly" although it is an invalid time. I can not right now do the
checking myself so the initila case described by this bug still remains a bug.
If the Time case set to something like Time=ttt, It will detect it and the
comments I made on comment2 would be valid.
I am setting it to FUTURE and revisit it later.

10/19/04 16:08:53 changed by nsavard@mapgears.com 

Verified that all cases described in comment #2 works.