well finally I found the problem the xml result of the GetCapabilities request was containing a char that was wrongly coded as UTF-8 (this char :"è")
I manager to change this on the WMS server i was trying to do "Castading" and everything worked as always like a charm ________________________________________ Inizio: [email protected] [[email protected]] per conto di Andrea Aime [[email protected]] Inviato: martedì 29 novembre 2011 20.36 Fine: Pierluigi Santin Fintel Cc: [email protected] Oggetto: Re: [Geoserver-users] Cascading WMS (last version of geoserver) On Tue, Nov 29, 2011 at 4:32 PM, Pierluigi Santin Fintel <[email protected]> wrote: > > Hi i have a problem with cascading wms > > > > In the capabilities url I input the correct url > http://myserver/service/wms?Request=GetCapabilities > > If I key in this url in a web browser I correctly download the xml with the > capabilities > > > > But in WMS cascading Geoserver gives me an error > > > > Connection test failed: Server returned HTTP response code: 400 for URL: > http://myserver/service/wms?wmtver=1.0.0&request=capabilities > > > > Which is a url different from what I keyed in and if I write this on a > browser I have an http error 400. > > > > But why geoserver does not use my URL? A WMS client makes that single request you provided only if the version advertised by your WMS server matches one of the supported versions, which is reported in the root element of your capabilities document. If for example I provide a request like http://demo1.geo-solutions.it/playground/wms?request=GetCapabilities the client will make the request as is, and will find the following capabilities root element: <WMS_Capabilities xmlns="http://www.opengis.net/wms"; xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="1.3.0" updateSequence="1156" xsi:schemaLocation="http://www.opengis.net/wms http://demo1.geo-solutions.it:80/playground/schemas/wms/1.3.0/capabilities_1_3_0.xsd";> See version="1.3.0". Since 1.3.0 is one of the supported versions (along with 1.0.0, 1.1.0 and 1.1.1) that's the only capabilities request the client does. But if you don't provide a version or the one you provide is not supported the client will start the standard capabilities negotiation cycle, asking you for other versions that it supporst, and your server is supposed to answer with the proper OGC exception in case the version requested is not supported, not with a HTTP 400 Hope this helps Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
