TransportOption question

[Mike Flynn]

Running some tests this morning, I noticed that one of the federation's (UK Fed in this case) servers was slow returning the metadata during Shib startup and indeed, it timed out trying to fetch the data.  Hitting the URL for the data showed that it was taking about 90 seconds or more to return the data.

So, Googling around looking for how to control the CURL timeout, I found the TransportOption.  I added this to my config:

<MetadataProvider type="Chaining">
<TransportOption provider="CURL" option="13">120</TransportOption>

(first tag there is pre-existing).  Indeed this resolved the issue and all other metadata loaded just fine as well.  So, the question becomes, is this an appropriate adjustment to the config for this issue?  If so, are there any other ramifications that might affect my system based on the use of this stanza in the config?  There is nothing special about my Shib installation.  It's a generic, vanilla install.

I am running SP 2.3.1 on IIS7 - all 64 bit.

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140624/fa62dfd7/attachment.html