Harvest: OAI client should follow http->https redirect since oai server validation allows http.

[kcondon]

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.

[cmbz]

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.

[stevenferey]

Hello,

I tried to harvest an OAI server compatible with the HTTP protocol, e.g.: http://cds.unistra.fr/registry/?verb=ListIdentifiers&metadataPrefix=oai_dc

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.
In this case, an error is raised during harvesting :

Caused By Exception.................... java.nio.channels.UnresolvedAddressException null
StackTrace: 
java.base/sun.nio.ch.Net.checkAddress(Unknown Source)
java.base/sun.nio.ch.Net.checkAddress(Unknown Source)
java.base/sun.nio.ch.SocketChannelImpl.checkRemote(Unknown Source)

[pdurbin]

@stevenferey interesting. Are you considering creating a pull request to fix this? 😄

[stevenferey]

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?

[pdurbin]

Sure, if you're interested in this, I think a fresh issue would be nice.