search

Letractively / morisoliver

Automatically exported from code.google.com/p/morisoliver
0 stars 0 forks source link

Google Chrome doesn't show secured WMS layers #131

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Firefox, IE and Safari all ask the user for credentials (2 or 3 times) then 
show the secured datalayer on the map and offer the secured datalayer for 
editing (the layer will show up in the Draw and Edit menus). Chrome asks for 
credentials once, and at that point WFS is functional (can add and edit 
features to the secured datalayer) however, the WMS layer as the default layer 
remains with a red exclamation point.  If a new WMS request is made in a new 
tab credentials are requested and then the map is shown.  

If I remove the editable layer with the red exclamation point from the map and 
re-add it it doesn't prompt me for credentials - it remains with the red ! 
mark.  So currently there is no way for the user to see the datalayer.  (except 
for requesting the WMS in another tab and entering credentials, then coming 
back to the first tab the browser does display the datalayer).

Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 28 Feb 2012 at 6:50

GoogleCodeExporter commented 8 years ago 
Even with a local yui and all https references Chrome still only asks for the 
username / password once and then shows the edit layer with a red !

Original comment by Aleda.Fr...@state.ma.us on 1 Mar 2012 at 9:27

GoogleCodeExporter commented 8 years ago

Original comment by Aleda.Fr...@state.ma.us on 6 Mar 2012 at 6:20

GoogleCodeExporter commented 8 years ago

Original comment by Aleda.Fr...@state.ma.us on 28 Jun 2012 at 4:02

GoogleCodeExporter commented 8 years ago 
Can't use Chrome Frame if this is not fixed.

Original comment by Aleda.Fr...@state.ma.us on 28 Jun 2012 at 4:02

GoogleCodeExporter commented 8 years ago 
Saul says won't work in Safari either if it doesn't work in Chrome.

Original comment by Aleda.Fr...@state.ma.us on 9 Nov 2012 at 9:50

GoogleCodeExporter commented 8 years ago 
However it does.

Original comment by Aleda.Fr...@state.ma.us on 9 Nov 2012 at 9:53

GoogleCodeExporter commented 8 years ago 
After research and much coding, we discovered that Chrome will not force a 
authentication box if a 401 is received from an XHR or <img> tag.

Instead, we need to try another approach (perhaps catching the XHR's error and 
pushing a popup to the user?) if we're going to resolve this issue for chrome.

Original comment by its.s...@gmail.com on 9 Nov 2012 at 10:35