Opened 20 years ago

Closed 19 years ago

#657 closed defect (duplicate)

Hard-coded link in capabilities.xml to capabilities_1_1_0.dtd is broken

Reported by: info@… Owned by: mapserverbugs
Priority: high Milestone: 4.4 release
Component: WMS Server Version: 4.0
Severity: normal Keywords:
Cc: panos.panagos@…

Description

I'm using Mapserver as a WMS and since one week, the link to the 
capabilities_1_1_0.dtd

http://www.digitalearth.gov/wmt/xml/capabilities_1_1_0.dtd

is not available.

Because Mapserver is generating dynamically its capabilities-XML-file with this 
link by default inside, a GetCapabilities-Request produces an error.

It would be more comfortable to specify the path in the mapfile.

Change History (13)

comment:1 by panos.panagos@…, 20 years ago

I am using MapServ.exe 4.0
and WMS
If i do the GetCapabilities request:
http://eusoils.jrc.it/scripts/mapserv.exe?
map=c:///msapps/ESB_soil_maps//ESB_Soil.map&VERSION=1.1.1&REQUEST=GetCapabilitie
s
I get the Mapserv77.txt file

Which contains:
<!DOCTYPE WMT_MS_Capabilities 
SYSTEM "http://www.digitalearth.gov/wmt/xml/capabilities_1_1_0.dtd"

For a long time my map Viwer was able to run the WMS service.
Since a while i cannot run the WMS service
Is it a problem as the http://www.digitalearth.gov/ doesn't exist anymore?
How i can ask in my MAP file to be validated by another validator like 
http://www.stg.brown.edu/service/xmlvalid/?

thanks in advance,

comment:2 by dmorissette, 20 years ago

Cc: panos.panagos@… added

comment:3 by dmorissette, 20 years ago

*** Bug 659 has been marked as a duplicate of this bug. ***

comment:4 by dmorissette, 20 years ago

Milestone: 4.2 release
Status: newassigned
FYI Jeff DLB wrote the following note to the WMS-Dev list yesterday:

> The DNS entry for www.digitalearth.gov has been modified so
> that it points to a different machine
> (www2.digitalearth.gov) that has a copy of the DTDs.  This
> DNS change will propagate during the next ~24hrs around the
> internet.


So the DTD URL should work for you again very soon, it works for me now.

However we should still do something about this in MapServer, and ideally before
the 4.2 release.

comment:5 by assefa, 19 years ago

Daniel : Do we still want to do something about this before this release ?

comment:6 by panos.panagos@…, 19 years ago

Resolution: fixed
Status: assignedclosed
The proble during this momment was tha tthe site
http://www.digitalearth.gov/
was down....

Since it is working there isn o problem

comment:7 by dmorissette, 19 years ago

Milestone: 4.2 release4.4 release
Resolution: fixed
Status: closedreopened
I'll reopen since this is not really fixed and may become an emergency again if
digitalearth.gov ever goes down again.

However we won't do anything just now, we'll wait for OGC to post the DTDs to
http://schemas.opengeospatial.net/wms/ and then we'll use the
ows_schemas_location metadata to control the location of this DTD as well. 

I have sent a reminder a few minutes ago to a few key OGC people to try to get
them to post the DTDs in their schemas repository.

I'll set target milestone to 4.4 in the hope that this can be addressed in time
for 4.4, but if the OGC repository is not updated in time for the release then
we'll move the target to FUTURE.

comment:8 by dmorissette, 19 years ago

Status: reopenedassigned

comment:9 by dmorissette, 19 years ago

Cc: dmorissette@… added

comment:10 by dmorissette, 19 years ago

*** Bug 158 has been marked as a duplicate of this bug. ***

comment:11 by dmorissette, 19 years ago

Cc: tom.kralidis@… added
I just got an update that the DTDs are in the process of being added to
schemas.opengeospatial.net. Stay tuned.

comment:12 by dmorissette, 19 years ago

Note that we should also make sure we update the location of the exceptions DTD
(1.0.0 and 1.1.0), this was the topic of bug 158. 

comment:13 by dmorissette, 19 years ago

Resolution: duplicate
Status: assignedclosed
The schemas have been posted. However Tom filed another bug about this, but with
a complete list of schemas that we should point to, so I'll mark this onee as a
duplicate.

*** This bug has been marked as a duplicate of 999 ***
Note: See TracTickets for help on using tickets.