Hi,
This is how WMS is planned to be used:
1) Read the GetCapabilities document of the server. The request contains these
parts:
- base URL of the server
- &SERVICE=WMS
- &REQUEST=GetCapabilities
- &VERSION=x.x.x (optional, but if not given leads to version negotiation which
is not totally reliable in practise; I prefer to give the version explicitly)
WMS servers, like OpenJUMP, know to add service, request, and version to base
URL so the short url is enough. If a long, complete request is given as base
URL, what happens?
- Client may understand NOT to add service, request, and version for the second
time
- Or client may not understand that and the final request can be like
&SERVICE=WMS&SERVICE=WMS&VERSION=1.1.1&VERSION=1.1.1
- Double parameters may not have any bad effect on WMS server, but sometimes
they do; especially if the result is &VERSION=1.1.1&VERSION=1.3.0
- Sometimes if is good to give the long URL because it may the only way to
force WMS server to use a certain WMS version, for example 1.1.1.
2) If the first step was to read GetCapabilities, the second step is to build
layer list and read the GetMap URL from the GetCapabilities. That is the URL
that must be used for capturing the map images according to standard. GetMap
URL does not need to be the same as GetCapabilities URL. Usually they are, but
sometimes not. Sometimes, if they differ, it is an error and they should be the
same really.
Because OpenJUMP must do also GetMaps as user:[email protected]? it can not
use the advertised GetMap but use the base URL instead. Imagine now that the
base url is the long URL and contains &REQUEST=GetCapabilities. When building
on top of that the final GetMap could look like
&REQUEST=GetCapabilities&REQUEST=GetMap..
The server may have hard times when deciding what to do.
Now there are two special issues in the case of Andrei Nacu:
1) OpenJUMP does not support very well authentication. All it can do is to add
user:password before the base URL as
https://user:password@base_url.<https://user:password@base_url./> This is not
the same URL that is advertised for GetMap because GetCapabilities document
hopefully does not show the user name and password as plain text
2) The user:password in OpenJUMP is really tested only with https. Basic
authentication withour https does not make much sense because credentials are
too easy to capture from unsecured traffic. However, the server that Andrei is
using does exactly use basic auth over plain http.
I use all the time Basic auth over https with OpenJUMP and it does work well. I
thought that Michaël corrected an issue that prevented the use of basic auth
with plain http but it can be that it does not still work well. I have
difficulties in testing because if we use authentication we have only https
open in the firewall.
Sorry that I did not have enough time for studying the net traffic between
OpenJUMP and WMS server. Therefore what I wrote is partly based on old
experience and partly on plain guessing.
-Jukka Rahkonen-
________________________________
Lähettäjä: Andrei Nacu <[email protected]>
Lähetetty: 15. joulukuuta 2014 17:05
Vastaanottaja: OpenJump develop and use
Aihe: Re: [JPP-Devel] accessing a password protected WMS server
QGis 2.0 and Global Mapper v. 14 (tested by a friend).
In QGis the layer source properties indicate that both url's are accepted.
Andrei
On Monday, December 15, 2014 4:11 PM, "[email protected]"
<[email protected]> wrote:
A. what are the other 2 gis viewers, can you name them?
B. is it possible that they silently switch to the advertised, shorter url?
..ede
On 15.12.2014 14:39, Andrei Nacu wrote:
> Having checked the wms server today from Open JUMP and 2 other GIS viewers I
> see that the server can be accessed with both the shorter and longer address
> variants. Only Open JUMP can't open it from the longer address (the one with
> ”?service=wms&version=1.1.1&request=GetCapabilities”).
> The SRTM hillshade is unavailable from Open JUMP, as well as the other 2 GIS
> viewers.
> Andrei
>
>
> On Thursday, December 11, 2014 8:33 PM, Andrei Nacu
> <[email protected]<mailto:[email protected]>> wrote:
>
>
>
>
>
> The wms is not working today. I'll check on it when it is functional again.
> Yesterday the conclusion was that the shorter address variant (with wms
> instead of ows and without the
> ”?service=wms&version=1.1.1&request=GetCapabilities” part) allows us to view
> the wms map layers.
>
> Andrei
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Jump-pilot-devel mailing list
> [email protected]<mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Jump-pilot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
