We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Author Name: Giovanni Manghi (@gioman)
Sorry, something went wrong.
What is the status of this ticket @tomkralidis ? Did you switch to use the native QGIS network access manager ?
@Gustry no update, but we should keep open to be able to move into native QGIS HTTP/HTTPS handling.
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)
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: