Hi Goyo, I can take a look at this problem. However I'm a bit confused - the url you sent [1] *does* have a question mark in it. Have I misunderstood something?
> Also invalid request urls raise an HTTPError with code=404 which is > silently catched, resulting in call to log.debug raising a misleading > AttributeError. That's not great - I'll look into raising better errors. Thanks Dom On Monday 18 May 2009 19:16:39 Goyo wrote: > Hi all, > > I'm having problems using owslib.wcs module. Some broken services (see > [1] for an example) don't include question marks in urls and owslib > builds invalid request urls. > > The WCS 1.0.0 specification[2] states that clients should be prepared to > handle this broken behavoir: > > [Quote] > For HTTP GET, the URL prefix must end in either a '?' (in the > absence of additional server-specific parameters) or a '&'. In > practice, however, Clients should be prepared to add a necessary > trailing '?' or '&' before appending the Operation parameters > defined in this specification in order to construct a valid > request URL. > [End quote] > > Also invalid request urls raise an HTTPError with code=404 which is > silently catched, resulting in call to log.debug raising a misleading > AttributeError. > > Best regards > > Goyo > > [1] > http://www.idee.es/wcs/IDEE-WCS-UTM30N/wcsServlet?REQUEST=GetCapabilities&S >ERVICE=WCS&VERSION=1.0.0&SECTION=/WCS_Capabilities/Capability > > [2] Web Coverage Service (WCS), Version 1.0.0 (Corrigendum) > <http://portal.opengeospatial.org/files/?artifact_id=12582> > > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
