perfSONAR User Q&A and Other Discussion

[Brian Candler <>]

> I think the "500 timeout” is just a normal timeout, nothing from the 
server. I think 500 just got stuck in there because an eror code is 
expected in an object returned by that part of the code. Confusing for 
sure.

> I have never seen that "* additional stuff not fine transfer.c” 
before and I don’t get it when I run curl -v on my local host. Maybe a 
different version of curl? or is there a web proxy somewhere in the path 
doing weird stuff to requests? If that’s actually in the response body I 
am guessing the client will get confused.

No proxy. This is just an artefact of curl, see
http://stackoverflow.com/questions/13943181/why-is-curl-returning-additional-stuff-not-fine

It's running the stock version from Debian:

$ cat /etc/debian_version
7.9
$ curl --version
curl 7.26.0 (x86_64-pc-linux-gnu) libcurl/7.26.0 OpenSSL/1.0.1e 
zlib/1.2.7 libidn/1.25 libssh2/1.4.2 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 
pop3s rtmp rtsp scp sftp smtp smtps telnet tftp
Features: Debug GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz 
TLS-SRP

But I don't see it with curl under OSX, which is:

$ curl --version
curl 7.30.0 (x86_64-apple-darwin13.0) libcurl/7.30.0 SecureTransport 
zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps 
pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IPv6 Largefile NTLM NTLM_WB SSL libz

> Also the 403s you mentioned a few emails ago i wouldn’t stress over 
too much. Those sometimes happen if things are changing and there are 
still old records in the way. They age out within the hour and things 
should bounce back to normal.

OK, thanks.