Bug #6290
WMS and Proxy server issue
| Status: | New | Start Date: | 08/31/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | Version 2.0.0 | |||
| Platform: | Patch supplied: | No | ||
| Platform version: | Affected version: | 1.8.0 | ||
| Status info: | Causes crash or corruption: | No | ||
| Resolution: |
Description
We have an internal WMS server ( http://geognosis-vip/wms/wms.exe ) that we can access with several different clients. This being internal does NOT require use of the proxy server to access.
Somehow, QGIS has picked up some proxy settings and filled them in (I'm 99% certain I didn't), but I guess they're wrong because when I try and connect to the WMS it doesn't work.
In fact, what happens is, when I try and connect to the WMS it hangs QGIS, using fully 100% of a CPU core. If I close the WMS window using the little "x", QGIS remains hung and using 100% of the core. I don't think trying to negotiate with a proxy using incorrect credentials should cause the program to react so badly.
Note: I can work around this issue by disabling the proxy, or using the "exclude URLs" list.
p.s. I can't see an obvious "category" for this so have left it uncategorised.
History
Updated by Jonathan Moules 9 months ago
A related issue: It seems to make numerous attempts to connect to the proxy server with the same credentials, even when the given credentials don't already work. This results in the account being locked out, at least, with our network policy.
The correct thing to do would be to try once, and if the password is wrong, prompt the user for the correct password.
Updated by Paolo Cavallini 9 months ago
- Target version set to Version 2.0.0