- changed milestone to 1.2.0
get capabilities update without new login
Currently once logged in a click on get_capabilities always requests to enter the username/password again.
May be a capabilities update could become requested without the need to login again.
Comments (4)
-
reporter -
repo owner I think this was already fixed a while ago in wms_login_cache.py -- is there a bug in there?
-
The current behaviour allows a simple "return" to use a previously cached password. But the user is still presented with a dialog. As the dialog does not state this, nobody will find out. Also, switching servers prevents the caching from being effective. I propose to a) allow a configuration of username/password in the json config file (effectively pre-loading the cache server-specificly) b) try the cached password before presenting a dialog. I'll analyse the code some more and prepare a patch for this behaviour.
-
reporter - changed status to resolved
Better caching of login names per WMS server plus option to set them in config file. Resolves issue
#29→ <<cset 15af09405afa>>
- Log in to comment