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

Extent geoflow software to support request header(s) and http configs #238

Open
eblondel opened this issue Oct 15, 2021 · 2 comments
Open
Assignees

Comments

@eblondel
Copy link
Collaborator

eblondel commented Oct 15, 2021

geoflow software such as OGC web-service clients (eg. WPS) should support custom headers, depending on the client capabilities. In ows4R web service clients, we can add custom headers (eg. tokens). This has implication on geoflow-shiny interface for software, where key-value pairs should be handled for headers associated to software.

@eblondel eblondel self-assigned this Oct 15, 2021
@eblondel eblondel added this to the 1.0.0 milestone Dec 7, 2021
@eblondel eblondel removed this from the 1.0.0 milestone Feb 8, 2022
@eblondel eblondel changed the title Extent geoflow software to support custom request header(s) Extent geoflow software to support custom request header(s) and http configs Mar 14, 2022
@eblondel eblondel changed the title Extent geoflow software to support custom request header(s) and http configs Extent geoflow software to support request header(s) and http configs Mar 14, 2022
@eblondel
Copy link
Collaborator Author

same applies now with the config argument added in eblondel/ows4R#64

@eblondel
Copy link
Collaborator Author

cases with headers needs: WPSClient from ows4R, rapiclient for OpenAPI

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

1 participant