On Tue, May 8, 2018 at 11:24 AM, Gustaf Neumann <neum...@wu.ac.at> wrote:
> On 08.05.18 20:10, Ian Harding wrote:
>
> I tried with 4.99.16 and I have the same problem. Is the change you
> mention in that release or tip?
>
> The release of 4.99.16 was already on 2017-12-29. i would have used a
> different wording, when i would have referred to that! No, the change is on
> tip, as a response of your request...
>
Wow! Thank you. This works much better!
> -gn
>
>
> On Fri, May 4, 2018 at 11:52 AM, Gustaf Neumann <neum...@wu.ac.at> wrote:
>
>> On 04.05.18 18:44, Ian Harding wrote:
>>
>>
>>
>>> i will look into this in the near future
>>>
>>
>> Thank you! I think I'll have to keep using exec curl for the time
>> being...
>>
>> There is an updated version of NaviServer at bitbucket, which improves
>> the situation by leading to a consistent behavior of https and http from
>> the user perspective.
>>
>> One can now as well distinguish between "errors" and "timeouts" by using
>> try:
>>
>> try {
>> set r [ns_http run -timeout 0.01 http://google.com/]
>> } trap NS_TIMEOUT {msg} {
>> ns_log notice TIMEOUT
>> }
>>
>>
>> All the best
>>
>> -g
>>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> naviserver-devel mailing list
> naviserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
