I tried using a "fake oai server" for the harvester test in xmlui that was 
internal to our university and not only did it output something other than 
"OAI server could not be reached" (was "OAI did not respond to 
ListMetadataFormats query (:null ; :null): null"), but it didn't hang for a 
long time either. So I'm reasonably sure the problem is that it's not using 
our campus web proxy to contact the bepress oai server. Checked both the 
tomcat and dspace logs, but nothing in there related to this.

If someone knows which proxy settings the xmlui harvest test uses (tomcat, 
local.cfg or ???), I'd really appreciate it.

On Monday, October 4, 2021 at 1:32:20 PM UTC-7 Gavin Spomer wrote:

> When testing the settings for the harvester in DSpace 6.3 / xmlui, it 
> eventually times out with error "OAI server could not be reached". I'm 
> guessing it's because of being behind our campus web proxy, but I've 
> configured the host and port in both Tomcat's setenv.sh:
>
>    JAVA_OPTS="$JAVA_OPTS -Dhttp.proxySet=true -Dhttp.proxyHost=
> our.proxyhost.edu -Dhttp.proxyPort=3128"
>
> and my local.cfg file:
>
>    http.proxy.host = our.proxyhost.edu
>    http.proxy.port = 3128
>
> Shouldn't that be enough? Which proxy settings does the harvester in xmlui 
> use? 
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/0316388c-16b2-46ce-9d85-8ea1e56332fen%40googlegroups.com.

Reply via email to