Skip to content
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

implement QgsNetworkAccessManager for HTTP #24214

Open
qgib opened this issue Mar 7, 2017 · 4 comments
Open

implement QgsNetworkAccessManager for HTTP #24214

qgib opened this issue Mar 7, 2017 · 4 comments

Comments

@qgib
Copy link
Contributor

qgib commented Mar 7, 2017

Author Name: Tom Kralidis (@tomkralidis)
Original Redmine Issue: 16304

Redmine category:metasearch_catalogue_client
Assignee: Tom Kralidis


MetaSearch leverages OWSLib for CSW request/response handling which results in also using OWSLib's HTTP request/response handling.

Using QGIS' @QgsNetworkAccessManager@ provides numerous benefits (HTTP auth, proxy, etc.) in accessing the network in a uniform way via QGIS.

Update MetaSearch to implement @QgsNetworkAccessManager@. This will likely require changes to OWSLib as an initial step to abstract HTTP handling.

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0

@Gustry
Copy link
Contributor

Gustry commented Aug 27, 2021

What is the status of this ticket @tomkralidis ?
Did you switch to use the native QGIS network access manager ?

@gioman gioman added the Feedback Waiting on the submitter for answers label Aug 27, 2021
@tomkralidis
Copy link
Contributor

@Gustry no update, but we should keep open to be able to move into native QGIS HTTP/HTTPS handling.

@pathmapper
Copy link
Contributor

to be able to move into native QGIS HTTP/HTTPS handling

Would be great, given this is a core plugin.

Use behind http proxy seems to be broken for some reason -> #53159 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants