-
Notifications
You must be signed in to change notification settings - Fork 495
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
Harvest: OAI client should follow http->https redirect since oai server validation allows http. #4831
Comments
To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'. If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment. |
Hello, I tried to harvest an OAI server compatible with the HTTP protocol, e.g.: Tested with the devleop branch, it is not possible to fill in an OAI server with the HTTP protocol : It is however possible to declare a harvesting client with the API and fill in an OAI server with the HTTP protocol.
|
@stevenferey interesting. Are you considering creating a pull request to fix this? 😄 |
This is not planned by the team at the moment ! Do you want a new issue to be created to allow OAI server harvesting with HTTP protocol? |
Sure, if you're interested in this, I think a fresh issue would be nice. |
@stevenferey thanks for creating this new issue: |
Configuring an oai client allows http to be used in oai server url, as long as the server is valid. However, the actual harvest fails when it receives a 302 to move to https.
The text was updated successfully, but these errors were encountered: