Bug report #8600
QGIS 2.0 not working with NTLM proxy
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||windows ubuntu||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||17342|
When using the python plugin installer with QGIS 1.8 I could authenticate using our corporate NTLM proxy server by entering the following network proxy details: host, port, username, password and selecting HttpProxy. But now under QGIS this is not possible. I see that the new plugin installer was switched over the using the QgsNetworkAccessManager in this 4ecf3ebd0bae19f97f32bb040c9df95967135ba8
Going back and checking WFS and WMS (which use QgsNetworkAccessManager) with QGIS 1.8 I can't actually get proxy support working. So the problem must be that the QgsNetworkAccessManager is not set-up to authenticate with a NTLM proxy server.
This bug should be treated as critical because it will stop a lot of corporates from using QGIS.
#3 Updated by Giovanni Manghi over 7 years ago
- Status changed from Open to Feedback
is this really a regression or it wasn't supported either on older qgis releases?
The blocker tag is reserved for regression, so if it isn't, in order to clean the bug queue for this month of bug fixing prior 2.2, I guess it would be needed to lower the priority.