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
requests
As a user, I want to use geoserver-rest with a GeoServer instance that provides self-signed SSL certificates.
As a user, I would like to customize the functions using the requests package to set verify=False, see docs.
verify=False
A possible solution would be to accept a **kwargs in the user-facing APIs, e.g. get_featurestore
**kwargs
get_featurestore
geoserver-rest/geo/Geoserver.py
Line 2050 in d07ee02
and pass those **kwargs to the requests call
Line 2062 in d07ee02
so that users could do get_featurestore(..., verify=False).
get_featurestore(..., verify=False)
The text was updated successfully, but these errors were encountered:
Hi @fleimgruber, I like the idea. Feel free to raise the PR if you want.
Sorry, something went wrong.
that sounds great
No branches or pull requests
As a user, I want to use geoserver-rest with a GeoServer instance that provides self-signed SSL certificates.
As a user, I would like to customize the functions using the
requests
package to setverify=False
, see docs.A possible solution would be to accept a
**kwargs
in the user-facing APIs, e.g.get_featurestore
geoserver-rest/geo/Geoserver.py
Line 2050 in d07ee02
and pass those
**kwargs
to therequests
callgeoserver-rest/geo/Geoserver.py
Line 2062 in d07ee02
so that users could do
get_featurestore(..., verify=False)
.The text was updated successfully, but these errors were encountered: