-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WMS and Proxy server issue #15588
Comments
Author Name: Jonathan Moules (Jonathan Moules) 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. |
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Jürgen Fischer (@jef-n) Is this still valid?
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n) closing for the lack of feedback.
|
Author Name: Jonathan Moules (Jonathan Moules)
Original Redmine Issue: 6290
Affected QGIS version: 1.8.0
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.
The text was updated successfully, but these errors were encountered: