Malformatted url responses by SWORD API

[chStaiger]

I installed a dataverse testserver and using port 8080 for HTTP requests as suggested in the install guide. I observe some strange behaviour when using the FQDN or IP address for posting requests for datasets:

When I am using 'localhost' to list a dataset the request answer is as expected:

curl -u $TOKEN: http://localhost:8080/dvn/api/data-deposit/v1.1/swordv2/statement/study/hdl:21.T12995/KODBWV

<feed xmlns="http://www.w3.org/2005/Atom"><id>https://localhost:8080/dvn/api/data-deposit/v1.1/swordv2/edit/study/hdl:21.T12995/KODBWV</id><link href="https://localhost:8080/dvn/api/data-deposit/v1.1/swordv2/edit/study/hdl:21.T12995/KODBWV" rel="self"/><title type="text">New Test</title><author><name>Staiger, Christine</name></author><updated>2018-04-15T11:33:02.986Z</updated><category term="latestVersionState" scheme="http://purl.org/net/sword/terms/state" label="State">DRAFT</category><category term="locked" scheme="http://purl.org/net/sword/terms/state" label="State">false</category><category term="isMinorUpdate" scheme="http://purl.org/net/sword/terms/state" label="State">true</category></feed>

However, when using the ip address, the answer looks like this:

curl -u $TOKEN: http://$HOSTNAME:8080/dvn/api/data-deposit/v1.1/swordv2/statement/study/hdl:21.T12995/KODBWV

<feed xmlns="http://www.w3.org/2005/Atom"><id>https://145.100.59.118:8080:8080/dvn/api/data-deposit/v1.1/swordv2/edit/study/hdl:21.T12995/KODBWV</id><link href="https://145.100.59.118:8080:8080/dvn/api/data-deposit/v1.1/swordv2/edit/study/hdl:21.T12995/KODBWV" rel="self"/><title type="text">New Test</title><author><name>Staiger, Christine</name></author><updated>2018-04-15T11:33:02.986Z</updated><category term="latestVersionState" scheme="http://purl.org/net/sword/terms/state" label="State">DRAFT</category><category term="locked" scheme="http://purl.org/net/sword/terms/state" label="State">false</category><category term="isMinorUpdate" scheme="http://purl.org/net/sword/terms/state" label="State">true</category></feed>

For some reasons the API doubles the port.

[pdurbin]

@chStaiger thanks for opening this issue! As I mentioned at IQSS/dataverse-client-python#46 (comment) this is due to the SWORD API having "https" hard coded and how it sometimes puts in a port when it shouldn't: https://github.com/IQSS/dataverse/blob/v4.8.6/src/main/java/edu/harvard/iq/dataverse/api/datadeposit/UrlManager.java#L185

The workaround for now is to use https://demo.dataverse.org for testing APIs or to install a test server running https and having the dataverse.siteUrl JVM option set to not have a port (so that it runs on the standard https port ( https://dataverse.example.edu or whatever). Please see

• http://guides.dataverse.org/en/4.8.6/installation/config.html#dataverse-siteurl
• http://guides.dataverse.org/en/4.8.6/installation/config.html#network-ports

Sorry for the inconvenience!

[pdurbin]

@chStaiger is the workaround I described above enough for you or are you still interested in a fix?

[chStaiger]

The workaround works and I also added some extra lines in the python API to be sure that if Dataverse is not configured that way, that the python api calls are formed correctly.
See here: https://github.com/chStaiger/iBridges/blob/f10b0907b74b6cc627e4842fc08eca1003577253/clients/dataverse/dataverse.py#L16

[pdurbin]

@chStaiger ok. At some point we should remove the hard-coded "https" but I'm glad you figured out a workaround!

[pdurbin]

At some point we should remove the hard-coded "https"

I just mentioned this at #6296 (comment)