On Thu, Sep 18, 2014 at 11:32 AM, Rahkonen Jukka (Tike) <
[email protected]> wrote:
> Hi,
>
>
>
> I made some tests with two servers (http://demo.mapserver.org/cgi-bin/wms)
> and our own Mapserver v. 6.4.
>
> I feel that Andrea managed to resolve at least most problems. There may be
> something left with schema validation though https + basic auth but I am
> not sure about that. There is also a trouble with cascading GetFeatureInfo:
> Geoserver is sendind the request by using
> INFO_FORMAT=application/vnd.ogc.gml and there is probably no way to change
> that. Mapservers usually (ever?) do not support that info_format and
> GetFeatureInfos fail. Most common info_formats are text/plain and
> text/html. I believe this is a missing feature and not a new bug in
> Geoserver.
>
Correct, we need to get back a parseable data structure, since our feature
info "sources" generate a geotools featurecollection: there is no way
currently to just
cascade the other server featureinfo... and it's generally speaking not
fully trivial too.
What if I'm requested multiple layers, a bit local, a bit remote, in html
format, how am I going to build the result? The remote html could contain a
full
head section with css (like geoserver does) that we'd somehow have to merge
with ours.
>
>
> Tests results:
>
>
>
> - An old Mapserver version 5.6.5 in (http://demo.mapserver.org/cgi-bin/wms).
> It seems to be easier to set up test servers than to update them to recent
> versions, demo.opengeo.org is running Geoserver 2.4 SNAPSHOT.
>
> - First SRS is EPSG:4326, supports also EPSG:3857 and a few other.
>
> - The server contains
> http://demo.mapserver.org/cgi-bin/wms?service=WMS&version=1.3.0&request=GetSchemaExtension
>
> in WMS 1.3.0 GetCapabities.
>
>
>
> - Connection as WMS 1.3.0 PASSED
>
> - Connection as WMS 1.1.1 PASSED
>
> - Cascading WMS 1.3.0 as EPSG:4326 PASSED
>
> - Cascading WMS 1.3.0 as EPSG:3857 PASSED
>
> - Cascading WMS 1.1.1 as EPSG:4326 PASSED
>
> - Cascading WMS 1.1.1 as EPSG:3857 PASSED
>
> - Cascading WMS 1.1.1 as EPSG:3067 (not natively supported) PASSED,
> Geoserver sends requests as EPSG:4326 and re-projects into target SRS
>
>
>
> Our own Mapserver 6.4.
>
> - Must be connected with https and basic auth
>
> - Supported projections for the test layer
>
> EPSG:2393
>
> EPSG:3067
>
> EPSG:4326
>
> EPSG:3857
>
> Server contains
> https://xxx.fi/cgi-bin/xxx?service=WMS&version=1.3.0&request=GetSchemaExtension”
> in WMS 1.3.0 GetCapabilities
>
>
>
> - Connection as WMS 1.3.0 NOT PASSED
>
> Error is “Connection test failed: Failed to resolve
> https://xxx.fi/cgi-bin/xxx?service=WMS&version=1.3.0&request=GetSchemaExtension
> ”
>
> This works with demo.mapserver.org and announced URL returns a document
> to browser. Could it be that schema resolving is not successful because of
> https + basic auth because that seems to be the only difference?go out with
> the
>
Could be... do you have a URL that I can hit, that allows reproducing the
issue?
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Slashdot TV. Video for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
